local tweaks

Author: shainaraskas

docs/contribute/cumulative-docs.md

@@ -13,19 +13,19 @@ With our markdown-based docs, there is no longer a new documentation set publish
 This new behavior starts with the following **versions** of our products: Elastic Stack 9.0, ECE 4.0, ECK 3.0, and even more like EDOT docs. It also includes our unversioned products: Serverless and Elastic Cloud.
 
 :::{note} 
-Nothing changes for our ASCIIDoc-based documentation system, that remains published and maintained for the following versions: Elastic Stack until 8.19, ECE until 3.8, ECK until 2.x, etc.
+Nothing changes for our ASCIIDoc-based documentation system, that remains published and maintained for the following versions: Elastic Stack until 8.x, ECE until 3.x, ECK until 2.x, etc.
 :::
 
 **How does it change the way we write docs?** 
 
 As new minor versions are released, we want users to be able to distinguish which content applies to their own ecosystem and product versions without having to switch between different versions of a page.
 
-This extends to deprecations and deletions: No information should be removed for supported product versions, unless it was never accurate. It can be refactored to improve clarity and flow, or to accommodate information for additional products, deployment types, and versions as needed.
+This extends to deprecations and removals: No information should be removed for supported product versions, unless it was never accurate. It can be refactored to improve clarity and flow, or to accommodate information for additional products, deployment types, and versions as needed.
 
 In order to achieve this, the markdown source files integrate a tagging system meant to identify:
 
-* [Which Elastic products and deployment models the content applies to](#tagging-products-and-deployment-models).  
-* [When a feature goes into a new state as compared to the established base version](#tagging-version-related-changes-mandatory).
+* [Which Elastic products and deployment models the content applies to](#tagging-products-and-deployment-models) (for example, Elastic Cloud Serverless or Elastic Cloud Hosted).  
+* [When a feature goes into a new state as compared to the established base version](#tagging-version-related-changes-mandatory) (for example, being added or going from Beta to GA).
 
 This tagging system is mandatory for all of the public-facing documentation. We refer to it as “[applies_to](https://elastic.github.io/docs-builder/syntax/applies/)” tags or badges.
 

docs/contribute/deployment-models.md

@@ -4,7 +4,7 @@ navigation_title: Choose a deployment model
 
 # Choose the docs deployment model for a repository
 
-With Docs V3 (elastic.co/docs), a single branch is published per repository. This branch is set to `main` (or `master`) by default. This is known as the continuous deployment model. However, it is possible to instead publish a different branch, also known as the tagged deployment model. 
+With Docs V3 (elastic.co/docs), a single branch is published per repository. This branch is set to `main` by default. This is known as the continuous deployment model. However, it is possible to instead publish a different branch, also known as the tagged deployment model. 
 
 On this page, you'll learn how to choose the right deployment model for your repository, and how to change the deployment model. You'll also learn about the workflows for working in each deployment model.
 

docs/contribute/index.md

@@ -33,7 +33,7 @@ In April 2025, we released our new documentation site. This site includes docume
 
 #### Branches in V3
 
-In Docs V3, a single branch is published per repository. This branch is set to `main` (or `master`) by default, but it is possible to instead publish a different branch by changing your repository's deployment model. You might want to change your deployment model so you can have more control over when content added for a specific release is published.
+In Docs V3, a single branch is published per repository. This branch is set to `main` by default, but it is possible to instead publish a different branch by changing your repository's deployment model. You might want to change your deployment model so you can have more control over when content added for a specific release is published.
 
 [Learn more about deployment models](deployment-models.md).
 

docs/migration/versioning.md

@@ -17,7 +17,7 @@ In this new system, documentation is written **cumulatively**. This means that a
 
 ## Deployment models
 
-In Docs V3, a single branch is published per repository. This branch is set to `main` (or `master`) by default, but it is possible to instead publish a different branch by changing your repository's deployment model. You might want to change your deployment model so you can have more control over when content added for a specific release is published. 
+In Docs V3, a single branch is published per repository. This branch is set to `main` by default, but it is possible to instead publish a different branch by changing your repository's deployment model. You might want to change your deployment model so you can have more control over when content added for a specific release is published. 
 
 * [Learn how to choose the right deployment model for your repository](/contribute/deployment-models.md)
 * [Learn how to set up your selected deployment model](/configure/deployment-models.md)