fix

Author: shainaraskas

docs/configure/deployment-models.md

@@ -33,7 +33,7 @@ Tagged deployment
 
 ### Continuous deployment
 
-This is the default. To get started, follow our [guide](guide/index.md) to set up the new docs folder structure and CI configuration
+This is the default. To get started, follow our [guide](/migration/guide/index.md) to set up the new docs folder structure and CI configuration.
 
 Once setup ensure the repository is added to our `assembler.yml`  under `references`. 
 
@@ -69,7 +69,7 @@ references:
 ```
 
 :::{note}
-In order for `9.0` to be onboarded it needs to first follow our [migration guide](guide/index.md) and have our documentation CI integration setup.
+In order for `9.0` to be onboarded it needs to first follow our [migration guide](/migration/guide/index.md) and have our documentation CI integration setup.
 Our CI integration checks will block until `current` is successfully configured
 :::
 

docs/contribute/cumulative-docs.md

@@ -53,7 +53,7 @@ When the context differs from what was specified at the page level in a specific
 
 * Likewise, when the difference is specific to just one paragraph or list item, the same rules apply. Just the syntax slightly differs so that it stays inline:
 
-  :::{include} _snippets/line-level-applies-example.md
+  :::{include} /syntax/_snippets/line-level-applies-example.md
   :::
 
 ### When should I indicate that something is NOT applicable to a specific context?
@@ -109,7 +109,7 @@ For this case, no specific version tagging is necessary.
 **A new feature is added to {{serverless-short}} or {{ecloud}}. How do I tag it?**  
 Cumulative documentation is not meant to replace release notes. If a feature becomes available in {{serverless-short}} and doesn’t have a particular lifecycle state to call out (preview, beta, deprecated…), it does not need specific tagging.
 
-However, in this scenario, it is important to consider carefully [when the change is going to be published](#choose-the-docs-deployment-model-for-a-repository).
+However, in this scenario, it is important to consider carefully [when the change is going to be published](deployment-models.md).
 
 We do not do date-based tagging for unversioned products.