Merge branch 'main' into crosslinks-in-toc-take-three

Author: theletterf

config/legacy-url-mappings.yml

@@ -8,7 +8,7 @@ stack: &stack [ '9.0+', '8.19', '8.18', '8.17', '8.16', '8.15', '8.14', '8.13',
 
 mappings:
   en/apm/agent/android/: [ '1.2.0' , '0.x' ]
-  en/apm/agent/dotnet/: [ '1.32.0', '1.8' ]
+  en/apm/agent/dotnet/: [ '1.33.0' ]
   en/apm/agent/go/: [ '2.7.1', '1.x', '0.5' ]
   en/apm/agent/java/: ['1.54.0', '0.7', '0.6']
   en/apm/agent/nodejs/: [ '4.x', '3.x', '2.x', '1.x' ]

docs/contribute/cumulative-docs/guidelines.md

@@ -185,7 +185,7 @@ Here are some common scenarios you might come across:
 % Source: https://github.com/elastic/kibana/pull/229485/files#r2231876006
 * **Do _not_ use version numbers in prose**.
   Avoid using version numbers in prose adjacent to `applies_to` badge to prevent
-  confusion when the badge is rended with `Planned` ahead of a release.
+  confusion when the badge is rendered with `Planned` ahead of a release.
 * **Cumulative documentation is not meant to replace release notes.**
   * For example, if a feature becomes available in {{serverless-short}} and
     doesn’t have a particular lifecycle state to call out (preview, beta, deprecated…),