docs: remove trailing content on doc pages

Author: jondricek

docusaurus/docs/contributing/coding-style.md

@@ -42,3 +42,5 @@ Prefix your commit with one of the following:
 
 The library is compiled with `"strict": true` and imports must be path-alias aware (`@/…`).
 Run `npm run build` to catch any type errors locally.
+
+---

docusaurus/docs/contributing/dev-setup.md

@@ -31,3 +31,5 @@ npm run test   # vitest tests
 
 You are now ready to hack on the library.
 Continue with [Coding Style & Linting](coding-style.md) for the mandatory style rules.
+
+---

docusaurus/docs/contributing/docs.md

@@ -39,3 +39,5 @@ Its pretty easy to add a new guide. Basically just do the following:
 
 1. Create your Markdown file inside `docusaurus/docs/<topic>/my-guide.md`
 2. Update `sidebars.ts` to include it
+
+---

docusaurus/docs/contributing/index.md

@@ -10,3 +10,5 @@ It complements the high-level `CONTRIBUTING.md` in the root of the repository by
 ## Topics
 
 <DocCardList />
+
+---

docusaurus/docs/contributing/tests.md

@@ -38,3 +38,5 @@ When adding new schemas or refinement logic:
 
 1. Write **positive** test cases (`schema.parse` passes)
 2. Write **negative** test cases that assert specific error messages
+
+---

docusaurus/docs/how-to-guides/error-handling.md

@@ -698,11 +698,3 @@ main().catch(console.error);
 ```
 
 ---
-
-## Next Steps
-
-- **Bundle Validation**: Learn how to [validate custom STIX bundles](./validate-bundles) before processing
-- **Schema Extension**: See how to [extend schemas with custom fields](./extend-schemas) for enhanced error detection
-- **Reference**: Check the [complete API documentation](../reference/) for error handling methods
-
-Your application now handles errors gracefully and provides reliable ATT&CK data access even in challenging environments!

docusaurus/docs/how-to-guides/index.md

@@ -14,5 +14,3 @@ These guides provide direct solutions to common problems you'll encounter when w
 <DocCardList />
 
 ---
-
-**Can't find what you're looking for?** Consider [opening a GitHub Issue](https://github.com/mitre-attack/attack-data-model/issues/new) to request a new how-to guide.

docusaurus/docs/how-to-guides/manage-data-sources.md

@@ -403,5 +403,3 @@ async function loadWithMonitoring(config: any) {
 - [Performance Optimization](./performance) - Scale for large datasets
 
 ---
-
-**You're now equipped to manage ATT&CK data sources effectively in any environment!**

docusaurus/docs/how-to-guides/performance.md

@@ -534,5 +534,3 @@ const config = {
 - [Reference: Configuration](../reference/configuration) - All configuration options
 
 ---
-
-**You're now equipped to scale the ATT&CK Data Model for production workloads!**

docusaurus/docs/how-to-guides/validate-bundles.md

@@ -407,11 +407,3 @@ echo "✅ All bundles validated successfully"
 ```
 
 ---
-
-## Next Steps
-
-- **Error Handling**: Learn [how to handle parsing errors gracefully](./error-handling)
-- **Schema Extension**: See [how to extend schemas with custom fields](./extend-schemas)
-- **Reference**: Check the [complete API documentation](../reference/)
-
-Your custom STIX bundles should now validate correctly and load reliably in the ATT&CK Data Model!