Proofread

Author: adam-dupaski

content/en/docs/addons/ats-addon/ht/v2/ht-two-getting-started.md

@@ -114,7 +114,7 @@ The **Test Cases** menu has three tabs:
 | --- | --- |
 | **Repository** | Here you create and store all your test cases, test suites, and custom actions. It is the ATS filing system, the heart of ATS. |
 | **Test Data** | Where you can create folders, actions, and enumerations.  |
-| **Stories** | Where you can access the sprints of your app. |
+| **Stories** | Where you can access the Sprints of your app. |
 
 In this how-to, only the **Repository** tab is described. 
 

content/en/docs/addons/ats-addon/rg-ats/v1/rg-one-projects.md

@@ -63,4 +63,4 @@ There are three sections on the dashboard. The upper-left section (1) shows you
 
 ## 6 Developer Portal integration
 
-Projects in ATS can be connected to Mendix Developer Portal projects. If this is done, ATS will fetch all sprints and user stories from the project. This allows you to connect your test cases to user stories.
+Projects in ATS can be connected to Mendix Developer Portal projects. If this is done, ATS will fetch all Sprints and user stories from the project. This allows you to connect your test cases to user stories.

content/en/docs/apidocs-mxsdk/apidocs/feedback-api.md

@@ -28,7 +28,7 @@ Each call also requires the parameters 'username' and 'password'. These are the
 
 ### 2.1 AcceptFeedback
 
-This call **accepts** the specified feedback item. This means that the app team has accepted the feedback and added this feedback as a story to the sprint.
+This call **accepts** the specified feedback item. This means that the app team has accepted the feedback and added this feedback as a story to the Sprint.
 
 | Parameter Name | Parameter Type | Description |
 | --- | --- | --- |

content/en/docs/apidocs-mxsdk/apidocs/stories-api.md

@@ -7,7 +7,7 @@ weight: 60
 
 ## 1 Introduction
 
-The Mendix Stories API allows you to retrieve, create, and update the sprints, stories, and tasks in your Mendix projects.
+The Mendix Stories API allows you to retrieve, create, and update the Sprint, stories, and tasks in your Mendix apps.
 
 {{% alert color="info" %}}
 Each call also requires the parameters `username` and `password`. These are the public credentials you will find below; actual authentication of requests is done through API keys.
@@ -26,22 +26,22 @@ To use the API, you need to set up a **Consumed Web Service** using the WDSL for
 
 ### 2.1 Microflow CreateSprint
 
-This microflow creates a new sprint for the specified project and returns the ID of the new sprint.
+This microflow creates a new Sprint for the specified project and returns the ID of the new Sprint.
 
 | Parameter Name | Parameter Type | Description|
 | --- | --- | --- |
 | ApiKey | String | The API Key the application uses to access the Stories API for this project. |
-| DurationInWeeks | Integer/Long | Duration of the new sprint in weeks.|
-| Name | String | Name of the new sprint.|
+| DurationInWeeks | Integer/Long | Duration of the new Sprint in weeks.|
+| Name | String | Name of the new Sprint.|
 | ProjectID | String | The ID of the project. |
-| StartDate | Date and time | Start date for the new sprint. If not filled, the sprint will automatically start directly after * the previous sprint. (optional)|
-| StartsAfterSprint | Integer/Long | ID of the Sprint directly preceding the new sprint. |
+| StartDate | Date and time | Start date for the new Sprint. If not filled, the Sprint will automatically start directly after * the previous Sprint. (optional)|
+| StartsAfterSprint | Integer/Long | ID of the Sprint directly preceding the new Sprint. |
 
 * Return value – Integer/Long
 
 ### 2.2 Microflow CreateStory
 
-This microflow creates a new story in the specified sprint and returns the ID of the new story. Parameters: 
+This microflow creates a new story in the specified Sprint and returns the ID of the new story. Parameters: 
 
 | Parameter Name | Parameter Type | Description
 | --- | --- | --- |
@@ -50,7 +50,7 @@ This microflow creates a new story in the specified sprint and returns the ID of
 | Name | String | Name of the new story. 
 | Points | Enumeration StoryPoints | Number of story points. If left empty will be set to 1\. (_1/_2/_3/_5/_8/_13/_20/_40/_100, optional)
 | ProjectID | String | The ID of the project. 
-| SprintID | Integer/Long | The ID of the sprint. 
+| SprintID | Integer/Long | The ID of the Sprint. 
 | StoryType | Enumeration StoryType | The type of the story (Feature or Bug) 
 
 * Return value – Integer/Long
@@ -71,19 +71,19 @@ This microflow creates a new task for the specified story and returns the ID of
 
 ### 2.4 Microflow GetSprintByID
 
-This microflow retrieves a specific sprint. Parameters: 
+This microflow retrieves a specific Sprint. Parameters: 
 
 | Parameter Name | Parameter Type | Description
 | --- | --- | --- |
 | ApiKey | String | The API Key the application uses to access the Stories API for this project.
 | ProjectID | String | The ID of the project. 
-| SprintID | Integer/Long | The ID of the sprint.
+| SprintID | Integer/Long | The ID of the Sprint.
 
 * Return value – Sprint_Transient
 
 ### 2.5 Microflow GetSprints
 
-This microflow retrieves all sprints in a specific project. Parameters: 
+This microflow retrieves all Sprints in a specific project. Parameters: 
 
 | Parameter Name | Parameter Type | Description
 | --- | --- | --- |
@@ -94,13 +94,13 @@ This microflow retrieves all sprints in a specific project. Parameters:
 
 ### 2.6 Microflow GetStories
 
-This microflow retrieves all stories in a specific sprint. Parameters: 
+This microflow retrieves all stories in a specific Sprint. Parameters: 
 
 | Parameter Name | Parameter Type | Description
 | --- | --- | --- |
 | ApiKey | String | The API Key the application uses to access the Stories API for this project.
 | ProjectID | String | The ID of the project. 
-| SprintID | Integer/Long | The ID of the sprint for which stories are being retrieved.
+| SprintID | Integer/Long | The ID of the Sprint for which stories are being retrieved.
 
 * Return value – List of Story_Transient
 
@@ -149,7 +149,7 @@ This microflow updates a story with modified information. Parameters:
 | ApiKey | String | The API Key the application uses to access the Stories API for this project.
 | Description | String | Description of the story (optional) 
 | Name | String | Name of the story. 
-| ParentSprintID | Integer/Long | The ID of the sprint the story is in. 
+| ParentSprintID | Integer/Long | The ID of the Sprint the story is in. 
 | Points | Enumeration StoryPoints | Number of story points. (_1/_2/_3/_5/_8/_13/_20/_40/_100) 
 | ProjectID | String | The ID of the project. 
 | Status | Enumeration BacklogState | Status of the story, (Open/Started/Done)

content/en/docs/refguide7/desktop-modeler/desktop-modeler-overview.md

@@ -44,7 +44,7 @@ The table below describes all the available dockable window panes.
 | Get Started | Shows useful resources for getting started with the Mendix Modeler. |
 | Project Explorer | Shows the complete structure of your project including all documents inside the modules. By default the active document is always selected in the project explorer so you can quickly see where the document you are editing is in the tree. You can change this behavior in the **Edit** > **Preferences** window pane. |
 | Properties | Shows properties of the currently selected element. This is where a lot of editing in the Modeler takes place. |
-| Stories | For [Team Server](/refguide7/team-server/) enabled projects, this pane shows the stories of the current sprint. |
+| Stories | For [Team Server](/refguide7/team-server/) enabled projects, this pane shows the stories of the current Sprint. |
 | Toolbox | Shows the tools that can be used in the current editor. For example, in a page you can insert all kinds of widgets (for example, text box and data view) by dragging them from the **Toolbox** to your form. |
 | Variables (via Debug Windows) | You can view the current values of variables here when debugging your application. |
 

content/en/docs/refguide7/version-control/using-version-control-in-the-dm.md

@@ -100,7 +100,7 @@ In general, it is a good idea to commit after implementing one feature or fixing
 Committing results in a new revision in the repository. You can add the following information in the Desktop Modeler when you perform a commit, and this will be attached to the newly created revision:
 
 * A textual message. This should be a summary of the changes you made
-* A list of Developer Portal stories that relate to the commit. A small commit will probably relate to one story. The Modeler shows stories that are in the current sprint and do not have a status of *Done*. Adding the story to the commit will not change the state of the Developer Portal story. Setting the status to 'Done' must be done manually and depends on your *definition of done*.
+* A list of Developer Portal stories that relate to the commit. A small commit will probably relate to one story. The Modeler shows stories that are in the current Sprint and do not have a status of *Done*. Adding the story to the commit will not change the state of the Developer Portal story. Setting the status to 'Done' must be done manually and depends on your *definition of done*.
 
 {{< figure src="/attachments/refguide7/version-control/using-version-control-in-the-dm/2018-02-21_13-50-03.png" >}}
 

content/en/docs/refguide8/modeling/menus/view-menu/stories-pane.md

@@ -12,9 +12,9 @@ tags: ["Studio Pro", "stories", "stories pane"]
 
 ## 1 Introduction 
 
-For version control enabled projects (projects with Team Server or other SVN servers), the **Stories** pane displays the stories and tasks of the current [Sprint](/developerportal/collaborate/stories/). Stories, tasks, and sprints are created and managed in the Developer Portal. For more information on stories, see [Stories](/developerportal/collaborate/stories/). For more information on tasks, see the [Adding a Task to a Story](/developerportal/collaborate/stories/#adding-task) section in *Stories*. 
+For version control enabled projects (projects with Team Server or other SVN servers), the **Stories** pane displays the stories and tasks of the current [Sprint](/developerportal/collaborate/stories/). Stories, tasks, and Sprint are created and managed in the Developer Portal. For more information on stories, see [Stories](/developerportal/collaborate/stories/). For more information on tasks, see the [Adding a Task to a Story](/developerportal/collaborate/stories/#adding-task) section in *Stories*. 
 
-In the **Stories** pane, you can view the stories and tasks of the current sprint, show or hide done stories, open their details, change the status of the stories and tasks, and open documents connected to stories. 
+In the **Stories** pane, you can view the stories and tasks of the current Sprint, show or hide done stories, open their details, change the status of the stories and tasks, and open documents connected to stories. 
 
 The **Stories** pane consists of the top bar with various buttons and a table:
 

content/en/docs/releasenotes/developer-portal/_index.md

@@ -197,7 +197,7 @@ In Portfolio Management, you can do the following
 
 #### Improvements
 
-* We improved some empty states in the story details dialog box, epics details dialog box, archived sprint details dialog box, and archived story details dialog box in Epics.
+* We improved some empty states in the story details dialog box, epics details dialog box, archived Sprint details dialog box, and archived story details dialog box in Epics.
 
 ### September 15th, 2022
 
@@ -269,13 +269,13 @@ In Portfolio Management, you can do the following
 
     * Map your exact development process with fully customizable swimlanes
     * Use Scrum or Kanban – we support both!
-    * Set sprint goals and see all the basic sprint information on the board – if you are using Scrum
+    * Set Sprint goals and see all the basic Sprint information on the board – if you are using Scrum
     * Drag and drop stories on our brand new project board
     * Format stories in any way you want – for example, adding headers, links, and code blocks, linking specific stories, and using @ to mention people (notifications for this coming soon!)
     * Clone stories
     * Create and track the progress of epics
     * Archive single stories or whole swimlanes
-    * Easily search through your completed stories and get an overview of completed sprints in the archive
+    * Easily search through your completed stories and get an overview of completed Sprints in the archive
 
     You can try it out for any Mendix app. Your Scrum Master just needs to enable Epics in the [General Settings](/developerportal/collaborate/general-settings/#project-management). Please note it is not yet possible to migrate the data from Stories into Epics, so we recommend using it for new projects or iterations first – in this way you do not have to worry about the stories in your current backlog.
 
@@ -963,7 +963,7 @@ In Portfolio Management, you can do the following
 
 #### Webhooks Available
 
-* We have added the ability to create webhooks for your apps. These webhooks can be configured to send information when sprints change and/or stories change.
+* We have added the ability to create webhooks for your apps. These webhooks can be configured to send information when Sprints change and/or stories change.
 
 ### April 5th, 2019
 

content/en/docs/releasenotes/sdk/model-sdk/model-sdk-2.md

@@ -105,7 +105,7 @@ SDK version 2.2.0 and 2.2.1 were unpublished because they were published in a br
 | Impact | Description |
 | --- | --- |
 | Minor | Added support for Mendix 6.4.0 |
-| Low | Working copies that are connected to sprintr projects can now be deployed and their runtime status can be requested |
+| Low | Working copies that are connected to projects can now be deployed and their runtime status can be requested |
 | Low | Unit-loading now has an extra optional forceRefresh option. If set, it will then bypass the Mendix MOdel SDK cache, and get the fresh unit straight from the source/server. |
 | Minor | All classes that could be useful for reflection on the model are now exposed through `mendixmodelsdk`, so imports from `mendixmodelsdk/dist/sdk/internal/...` should no longer be needed. |
 | Minor | Private members (starting with an underscore `_`) were not available in the docs but were available in the public typings and therefore in the IDEs. This has been fixed. It should never be necessary to access these members. However, if you did access them you now need to access the object to `any` before the typechecker allows you to access these members. The method `allProperties()` is now available on all structures for reflection purposes. |

content/en/docs/studio8/collaboration/collaboration-buzz.md

@@ -47,7 +47,7 @@ You will be automatically taken to the Developer Portal. For more information on
 
 You can create a feedback item via the **Buzz** tab. Feedback items allow you to submit ideas, questions, or issues on the app, and let your team work on them in the Developer Portal. 
 
-In a thread in Studio Buzz, you and your team may conclude that the subject discussed needs more thorough refinement or needs to be postponed to be picked up in future sprints. In that case, a feedback item is a useful way to bring the item under attention of the product owner in the team. From there it can evolve into a story and be planned for a sprint. For more information on feedback items, see [Feedback Management](/developerportal/collaborate/feedback/), especially the [Adding a Feedback Item to Your Backlog](/developerportal/collaborate/feedback/#adding) section.  
+In a thread in Studio Buzz, you and your team may conclude that the subject discussed needs more thorough refinement or needs to be postponed to be picked up in future Sprints. In that case, a feedback item is a useful way to bring the item under attention of the product owner in the team. From there it can evolve into a story and be planned for a Sprint. For more information on feedback items, see [Feedback Management](/developerportal/collaborate/feedback/), especially the [Adding a Feedback Item to Your Backlog](/developerportal/collaborate/feedback/#adding) section.  
 
 To create a feedback item, do the following: