fix

Author: shainaraskas

docs/contribute/_snippets/tagged-warning.md

@@ -1,4 +1,4 @@
-:::{caution}
+:::{warning}
 Some repositories use a [tagged deployment model](deployment-models.md), which means that their docs are published from a branch that is not `main` or `master`. In these cases, documentation changes need to be made to `main` or `master`, and then backported to the relevant branches.
 
 For detailed backporting guidance, refer to the example in [Choose the docs deployment model for a repository](/contribute/deployment-models.md#workflow-2-make-docs-updates-when-the-repo-is-publishing-docs-from-a-version-branch).

docs/contribute/locally.md

@@ -155,7 +155,7 @@ We write docs in Markdown. Refer to our [syntax](../syntax/index.md) guide for t
 
 This documentation is **cumulative**. This means that a new set of docs is not published for every minor release. Instead, each page stays valid over time and incorporates version-specific changes directly within the content. [Learn how to write cumulative documentation](cumulative-docs.md).
 
-:::{include} tagged-warning.md
+:::{include} _snippets/tagged-warning.md
 :::
 
 ## Step 5: Push your changes [#step-five]

docs/contribute/on-the-web.md

@@ -38,7 +38,7 @@ For content hosted on elastic.co/docs, most conceptual and narrative content is
 4. Make the necessary updates.  
 5. Commit your changes and create a pull request.
 
-:::{include} tagged-warning.md
+:::{include} _snippets/tagged-warning.md
 :::
 
 ## What if I need to update docs in both systems?

docs/migration/versioning.md

@@ -8,7 +8,7 @@ To ensure a seamless experience for users and contributors, the new versioning a
 * **Version awareness**: The documentation team tracks and maintains released versions for all products in a central configuration file.
 * **Simplified contributor workflow**: For pages that apply to multiple versions or deployment types, we’ve optimized the contributor experience by reducing complexity. Contributors can now manage multi-context content with ease, without duplicating information or navigating confusing workflows.
 
-In this new system, documentation is written **cumulatively**. This means that a new set of docs is not published for every minor release. Instead, each page stays valid over time and incorporates version-specific changes directly within the content. [Learn how to write cumulative documentation](cumulative-docs.md).
+In this new system, documentation is written **cumulatively**. This means that a new set of docs is not published for every minor release. Instead, each page stays valid over time and incorporates version-specific changes directly within the content. [Learn how to write cumulative documentation](/contribute/cumulative-docs.md).
 
 ## Tag processing