Fix broken links and typos in the documentation (#471)

Author: sunnynagavo

content/documentation/explanations/conformance-testing.md

@@ -13,7 +13,7 @@ You may have experienced the frustration of deploying to production, only to dis
 
 As introduced in [Main Concepts](/documentation/overview/main-concepts), Microcks can be used for **Contract conformance testing** of API or services under development. You spend a lot of time describing request/response pairs and matching rules: it would be a shame not to use this sample as test cases once development is underway!
 
-On the internet, you can find many different representations of how the different testing techniques relate to one another and should ideally be combined into a robust testing pipeline. At Microcks, we particularly like the Watirmelon representation below. Microcks enables you to automate **Automated API Tests** and focus specifically on **Contract conformance testing**.
+On the internet, you can find many different representations of how the different testing techniques relate to one another and should ideally be combined into a robust testing pipeline. At Microcks, we particularly like the Watermelon representation below. Microcks enables you to automate **Automated API Tests** and focus specifically on **Contract conformance testing**.
 
 <br/>
 <div align="center">

content/documentation/explanations/monitoring.md

@@ -51,7 +51,7 @@ Starting with Microcks `1.9.0`, we also provide a [Grafana](https://grafana.com/
 
 This dashboard uses data from a Prometheus source, so you don't have to enable the full OpenTelemetry support to use it. Standard Prometheus endpoints scraped by your Prom instance will do the job.
 
-Check the dedicated [/dashbaords](https://github.com/microcks/microcks/tree/master/observability/dashboards) on GitHub to get more details.
+Check the dedicated [/dashboards](https://github.com/microcks/microcks/tree/master/observability/dashboards) on GitHub to get more details.
 
 ## Benchmark suite
 

content/documentation/references/container-images.md

@@ -62,7 +62,7 @@ The *Uber* distribution provide additional tags with `-native` suffix (`xyz-nati
 
 ### Microcks Uber Async Minion
 
-The Microcks Uber Async Minion (`microcks-uber-async-minion`) is responsible for publishing mock messages corresponding to [AsyncAPI](/documentation/references/artifacts/asyncapi-conventions) definitions with *Uber* distribution. It is produced from https://github.com/microcks/microcks/tree/master/distro/uber-async repo folder.
+The Microcks Uber Async Minion (`microcks-uber-async-minion`) is responsible for publishing mock messages corresponding to [AsyncAPI](/documentation/references/artifacts/asyncapi-conventions) definitions with *Uber* distribution. It is produced from https://github.com/microcks/microcks/tree/master/distro/uber-async-minion repo folder.
 
 | Repository | Pull command      | Available tags |
 | ---------- | ----------------- | -------------- |

content/documentation/references/test-endpoints.md

@@ -27,8 +27,7 @@ Depending on your API/Service type and the protocol binding you want to connect
 
 ### Test Runner
 
-Microcks offers different strategies for running tests on endpoints where our microservice being developed are deployed. We recommend having a read at our explanations on [Conformance Testing](/documentation/explanations/conformance-testing/#conformance-metrics
-). Such strategies are implemented as **Test Runners**. Here are the default Test Runners available within Microcks:
+Microcks offers different strategies for running tests on endpoints where our microservice being developed are deployed. We recommend having a read at our explanations on [Conformance Testing](/documentation/explanations/conformance-testing/#conformance-metrics). Such strategies are implemented as **Test Runners**. Here are the default Test Runners available within Microcks:
 
 | <div style="width: 160px">Test Runner</div> | <div style="width: 160px">API & Service Types</div> | Description |
 | ----------- | ----------------- | ----------- |

content/documentation/references/testcontainers-modules.md

@@ -15,7 +15,7 @@ We try to setup and manage a unified roadmap between modules but because they ar
 
 This page lists the implementation status of various features by the different modules on July 21st, 2025. It will be updated regularly. 
 
-> 💡 Of course, **we welcome external contributions**! So, if you're in a hurry and need a missing feature, don't hesitate to propose a change and to submit a _Pull Pequest_ on the associated GitHub repository 🙏
+> 💡 Of course, **we welcome external contributions**! So, if you're in a hurry and need a missing feature, don't hesitate to propose a change and to submit a _Pull Request_ on the associated GitHub repository 🙏
 
 ## Initialization