Some grammar corrections

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/RICE-analysis-template.mdc

@@ -3,12 +3,12 @@ description: RICE prioritization of features using the Reach, Impact, Confidence
 alwaysApply: false
 ---
 # RICE Prioritization Template Instructions
-You will be prioritizing a list of features as an experience Product Manager using the RICE method, which calculates a Score based off of 4 metrics that you will provide values for.
+You will be prioritizing a list of features as an experienced Product Manager using the RICE method, which calculates a Score based off of 4 metrics that you will provide values for.
 
 ## Initial Features
 Before analyzing feature ideas using the RICE method, you first need to have a list of Features to prioritize.
 If the user hasn't provided you with a list of features, then you will first need to provide some feature ideas for them.
-Be sure to use the @product-context.mdc data for for initial context.
+Be sure to use the @product-context.mdc data for initial context.
 Inform the user that this template can help prioritize *up to 10* feature ideas at a time. If they provided a list of features, then tell them that you will take the first 10 features only. Or, provide a list of 10 feature ideas to be developed for the product. Provide the list in a numbered format.
 
 ## Business Goal

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/kpi-revenues-template.mdc

@@ -7,7 +7,7 @@ Before writing the KPI-Revenue Connector, ask a short Clarifying Question to the
 ONLY THEN, continue with the rest of this document. 
 **Also, advise the user that it may be better to manually switch to Gemini 2.5, which has a larger context window for this**
 
-Be sure to use the @product-context.mdc data for for initial context.
+Be sure to use @product-context.mdc data for for initial context.
 Then, sequentially answer the following sections to help create Metrics for a Product Manager to help explain the "Why" for a product:
 
 ## 1. Product Goals

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/lean-canvas-template.mdc

@@ -4,7 +4,7 @@ alwaysApply: false
 ---
 # Lean Canvas Template Instructions
 
-Be sure to use the @product-context.mdc data for initial context.
+Be sure to use @product-context.mdc data for initial context.
 When creating the Lean Canvas, while you are to take into account the Product Context, you can also modify the responses when thinking through the lean canvas sequentially.
 
 Then, create a Product Requirements Document, following this comprehensive structure:

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/persona-template.mdc

@@ -1,5 +1,5 @@
 ---
-description: Defining 2 User Personas for the product: Regular and Skeptical Personas
+description: Defining 2 User Personas for the product: Ideal and Skeptical Personas
 alwaysApply: false
 ---
 # Persona Template Instructions
@@ -19,7 +19,12 @@ For each of these last 5 categories, write 3 short 1-line bullets, no more than
 Next, write a skeptical User Persona for this product. Assume the persona is one of the listed target customers mentioned above,
 however, assume that it is someone who is not at all likely to like your product, as they are skeptical, 
 and it doesn't fit their needs and pains. Make sure to list: 
-1. Their name 2. Overview, 3. Goals, 4. Behaviors, 5. Pains and 6. Needs 
+1. Their name 
+2. Overview
+3. Goals
+4. Behaviors
+5. Pains
+6. Needs 
 For each of these last 5 categories, write 3 short 1-line bullets, no more than 10 words each. 
 
 Finally, write 3 short, Key Questions that you should ask potential users to help validate that this product is a good fit for them.

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/prd-template.mdc

@@ -3,7 +3,7 @@ description: Product Requirements Document, PRD, or Requirements Generator
 alwaysApply: false
 ---
 # PRD Template Instructions
-Before writing the User Stories, ask a short Clarifying Question to the user about what the Time Frame is for the feature, and what the Specific Feature is (do not provide ideas).
+Before writing the Product Requirements Document, ask a short Clarifying Question to the user about what the Time Frame is for the feature, and what the Specific Feature is (do not provide ideas).
 ONLY THEN, continue with the rest of this document.
 Be sure to use the @product-context.mdc data for initial context.
 Then, create a Product Requirements Document, following this comprehensive structure:
@@ -72,7 +72,7 @@ Milestone 1: Competitive Analysis, Make a list of 5 competitors and analyze thei
 In addition, write a single sentence what you think the greatest milestone *Risk* is for this project.
 
 ## 10. OKRs
-Provide 4 L1 and L2 OKRs to develop the feature or product. Each OKR should be a single sentence, no more than 25 words each.
+Provide OKRs as follows: 2 L1 Objectives. For each L1, provide 2 L2 Key Results (4 KRs total). Each line ≤ 25 words.
 Make sure that the OKRs are aligned with the features and the problem-solution set.
 Make sure that the OKRs are measurable and achievable, using the SMART criteria.
 

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-context.mdc

@@ -3,7 +3,7 @@ description: Product Context
 alwaysApply: true
 ---
 # Product Manager Document Generator - Product Context
-You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experience Product Manager.
+You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experienced Product Manager.
 
 ## Product Information
 **Product Name:** [GIVE IT A SHORT NAME]
@@ -35,7 +35,7 @@ You are to always consider the following Product Context information when replyi
 - [SOLUTION PART 3]
 
 ## Differentiator
-[LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY AND KEEP IT TO 1 OR 2 SENTENCES]
+[LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY TO KEEP IT TO ONE OR TWO SENTENCES]
 
 ## Product Summary
 [SUMMARIZE YOUR PRODUCT IN A SINGLE PARAGRAPH OF AROUND 100-200 WORDS. IT SHOULD INCLUDE THE ITEMS ABOVE AND CAN ALSO INCLUDE PARTS OF YOUR MISSION STATEMENT]

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-positioning.mdc

@@ -5,9 +5,9 @@ alwaysApply: false
 # Product Positioning Instructions
 Before writing the Product Positioning, ask a short Clarifying Question to the user about what the Specific Feature is (do not provide ideas).
 ONLY THEN, continue with the rest of this document.
-Be sure to use the @product-context.mdc data for for initial context.
+Be sure to use the @product-context.mdc data for initial context.
 Then, you will write 2 Elevator Pitches using the templates below. 
-Write only the pitch, no other text before or after the pitch. Try and refrain from using too many buzzwords and jargon, such as 'Say hello to", or "Say goodbye to", or using exclamations, such as "!" or "?!"
+Write only the pitch, no other text before or after the pitch. Try to refrain from using too many buzzwords and jargon, such as 'Say hello to", or "Say goodbye to", or using exclamations, such as "!" or "?!"
 
 ## 1. Crossing the Chasm Elevator Pitch
 Write an Elevator Pitch for the product, that is up to 100 words, using the template from the book 'Crossing the Chasm' by Gordon Moore, and follows the following structure: 

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/risk-analysis-template.mdc

@@ -2,17 +2,17 @@
 description: Risk Analysis
 alwaysApply: false
 ---
-Before writing the User Stories, ask a short Clarifying Question to the user about what the Specific Feature is (do not provide ideas).
+Before writing the Risk Analysis, ask a short Clarifying Question to the user about what the Specific Feature is (do not provide ideas).
 ONLY THEN, continue with the rest of this document.
-Be sure to use the @product-context.mdc data for for initial context.
+Be sure to use the @product-context.mdc data for initial context.
 You are performing Risk Analysis as a Senior Product Manager for the product, including all aspects of the product.
-Then, write a Risk Analysis for the Feature to be developed, using the this format:
+Then, write a Risk Analysis for the Feature to be developed, using this format:
 
 ## Risk Factor Categories
 Given the Product Context and Feature/Product to be developed, what are the three main risk categories involved in such a product?
 Some examples are: Technology, User Interface, Manufacturing, Logistics, Compliance, Legal and Strategic and others. 
-Do not list 'Product market fit' as one of them!
-List the three main risks categories first.
+Do not list 'Product Market Fit' as one of them!
+List the three main risk categories first.
 
 
 ## Risks and Mitigations:

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/roadmap-template.mdc

@@ -3,7 +3,7 @@ description: Roadmap planning
 alwaysApply: false
 ---
 # Roadmap Template Instructions
-Be sure to use the @product-context.mdc data for for initial context.
+Be sure to use the @product-context.mdc data for initial context.
 Use markdown to write the document, and short bullets for each item.
 When creating product Roadmaps, follow this comprehensive structure:
 

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-journey-template.mdc

@@ -5,9 +5,9 @@ alwaysApply: false
 # User Journey Template Instructions
 Before writing the User Journey, ask a short Clarifying Question to the user about what the Specific Feature is (do not provide ideas).
 ONLY THEN, continue with the rest of this document.
-Be sure to use the @product-context.mdc data for for initial context.
-You are writing the User Journey for the feature to be developed as a Product Manager with a speciality in UI and UX.
-Then, write a User Journey for the Feature to be developed, using the this format:
+Be sure to use @product-context.mdc data for initial context.
+Write the User Journey as a PM with a specialty in UI/UX.
+Then, write a User Journey for the Feature to be developed, using this format:
 
 ## 1. Phases of the Journey
 First you are looking to define the Phases of the journey, from the user's perspective. 
@@ -30,10 +30,10 @@ Write them in the first person, as if you were the user, without any extra text.
 Think about how the user interacts with the Product at each Phase. It could be in terms of how they use the application, or device, 
 or webpage, or how they address service. This is the Touchpoint that the user has with the product.
 Write the potential Touchpoints that the User has at each Phase. 
-For the TOUCHPOINTS, make each no more than 1 sentence of up to 12 words.
+For the Touchpoints, make each no more than 1 sentence of up to 12 words.
 
 ## 5. Opportunities
-For each of the Phases, What are the main Opportunities for improvement or development at this point/Phase? 
+For each of the Phases, what are the main Opportunities for improvement or development at this point/Phase? 
 List 3 different Opportunities as 3 single bullets, each a sentence of no more than 12 words, for each Phase.
 
 ## 6. Summary

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-story-template.mdc

@@ -5,8 +5,8 @@ alwaysApply: false
 # User Story and Acceptance Criteria Template Instructions
 Before writing the User Stories, ask a short Clarifying Question to the user about what the Specific Feature is (do not provide ideas).
 ONLY THEN, continue with the rest of this document.
-Be sure to use the @product-context.mdc data for for initial context.
-Then, write a User Story and Acceptance Criteria for the Feature to be developed, using the this format:
+Be sure to use the @product-context.mdc data for initial context.
+Then, write a User Story and Acceptance Criteria for the Feature to be developed, using this format:
 
 ## User Story
 Use the following format for the User Story:

rules/documentation-product-manager-multiuse-toolkit/alternate-templates/epic-alternate

@@ -9,13 +9,13 @@ Be sure to use the @product-context.mdc data for for initial context.
 When creating epics, follow this comprehensive structure, which lists the Epics first, and then provides some ideas for user stories.
 
 ## Epic Overview
-You are to generate the Epics for the product to match the time frame and scope. Try and define no more than *3* epics in total.
+You are to generate the Epics for the product to match the time frame and scope. Try to define no more than *3* epics in total.
 The epics should be different from each other, and should be in a way that is easy to understand. They should also be relevant to the product and feature scope.
 For each epic, you are to provide the following information:
 1. Provide a clear title following the format: "Epic: [Name]" 
 2. Include a brief description (1-2 sentences) explaining the purpose and scope
 3. Identify any major dependencies on other epics
-4. List the business unit in charge of this (eg, Design, Engineering, Marketing)
+4. List the business unit in charge of this (e.g., Design, Engineering, Marketing)
 
 List each epic similar to the Example below for only 2 epics, and additional epics should follow this style.
 ### Example Epic Output:
@@ -32,7 +32,7 @@ List each epic similar to the Example below for only 2 epics, and additional epi
 
 ## User Stories
 After writing the Epics, you will write some ideas for relevant User Stories for those Epics.
-Stop and think about the Epics you just wrote, and then come up with *5* User Stories each for each of the Epics.
+Stop and think about the Epics you just wrote, and then come up with *5* User Stories per Epic.
 Use the following format for the User Story:
 As a [type of user], I want to [perform some task] so that I can [achieve some goal].
 The User Story should be written in a tone that uses an Active Voice, and the Story is achievable.

rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.md

@@ -3,7 +3,7 @@ description: Product Context
 alwaysApply: true
 ---
 # Product Manager Document Generator - Product Context
-You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experience Product Manager.
+You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experienced Product Manager.
 
 ## Product Information
 **Product Name:** AgileGen
@@ -19,7 +19,7 @@ An extension for your coding IDE that allows you to use it instead for generatin
 ## Business Field
 - Productivity Tools
 - SaaS Technology
-- Product management software
+- Product Management Software
 
 ## Type of Business
 B2B

rules/documentation-product-manager-multiuse-toolkit/helper-docs/extra-copy-context.txt

@@ -3,7 +3,7 @@ description: Product Context
 alwaysApply: true
 ---
 # Product Manager Document Generator - Product Context
-You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experience Product Manager.
+You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experienced Product Manager.
 
 ## Product Information
 **Product Name:** [GIVE IT A SHORT NAME]
@@ -35,7 +35,7 @@ You are to always consider the following Product Context information when replyi
 - [SOLUTION PART 3]
 
 ## Differentiator
-[LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY AND KEEP IT TO 1 OR 2 SENTENCES]
+[LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY TO KEEP IT TO ONE OR TWO SENTENCES]
 
 ## Product Summary
 [SUMMARIZE YOUR PRODUCT IN A SINGLE PARAGRAPH OF AROUND 100-200 WORDS. IT SHOULD INCLUDE THE ITEMS ABOVE AND CAN ALSO INCLUDE PARTS OF YOUR MISSION STATEMENT]

rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt

@@ -113,7 +113,7 @@ The difference between the lifetime value of a customer (LTV) and the cost of ac
 
 *Monthly Recurring Revenue (MRR) 
 The predictable revenue generated by a subscription-based product on a monthly basis.  
-*Annial Recurring Revenue (ARR)
+*Annual Recurring Revenue (ARR)
 
 *Expansion Revenue 
 Additional revenue generated from existing customers, through upsells, cross-sells, or add-on purchases.