Merge pull request #29 from embrace-io/hho/broke-android-anchors

Fix broken anchor links on Android docs

docs/android/changelog.md

@@ -142,7 +142,7 @@ API Desugaring is now a requirement for apps that support Android 5 and 6. This
 ## 6.4.0
 *March 6, 2024*
 - Performance Tracing improvements
-    - Support configuration of OpenTelemetry Exporters to export [Performance Tracing](/android/features/tracing/#export-your-telemetry) data as OpenTelemetry Spans (beta).
+    - Support configuration of OpenTelemetry Exporters to export [Performance Tracing](/android/features/tracing/#export-to-opentelemetry-collectors) data as OpenTelemetry Spans (beta).
     - Change timestamps parameters of the APIs to use milliseconds to better align with Android developer expectations. 
         - Note: timestamps that are in nanoseconds will be detected and converted for now so existing instrumentation will still work, but this will be removed in an upcoming release.
     - Increase per-session limit of spans to 500 in total.
@@ -389,7 +389,7 @@ This version has a known issue with Gradle < 6.2
 ## 5.7.0
 *Oct 03, 2022*
 
-* New mechanism to auto-install Embrace dependencies. If you prefer to use the old mechanism, the new API can be disabled by setting the `useNewDependencyInstaller` property to false. You can check our documentation [**here**](/android/features/build-options#useNewDependencyInstaller-bool)
+* New mechanism to auto-install Embrace dependencies. If you prefer to use the old mechanism, the new API can be disabled by setting the `useNewDependencyInstaller` property to false.
 
 ## 5.6.2
 *Oct 03, 2022*

docs/android/faq.md

@@ -217,15 +217,15 @@ Please refer to [Performance Tracing feature guide](/android/features/tracing) f
 
 ### **Can I disable the capture of tap coordinates?**
 
-Yes, you can turn off capture of tap coordinates with the [`taps[capture_coordinates]` setting](/android/features/configuration-file#tapscapture_coordinates) in the `embrace-config.json` file.
+Yes, you can turn off capture of tap coordinates with the [`taps[capture_coordinates]` setting](/android/features/configuration-file/#capture_coordinates-bool) in the `embrace-config.json` file.
 
 ## Trace IDs
 
 ### **Can trace IDs for network requests be captured?**
 
 Yes, you can capture trace IDs in two ways:
 1. Add a trace ID to a request by adding the `x-emb-trace-id` header with the trace ID value
-1. If the ID is already present in the request in a different header, set the name of the header in the `embrace-config.json` file with the [`networking[trace_id_header]` setting](/android/features/configuration-file#networkingtrace_id_header)
+1. If the ID is already present in the request in a different header, set the name of the header in the `embrace-config.json` file with the [`networking[trace_id_header]` setting](/android/features/configuration-file/#trace_id_header-string)
 
 :::note
 Trace IDs longer than 64 characters will be truncated

docs/android/integration/crash-reporting.md

@@ -9,7 +9,7 @@ description: Upload crash reports from your Android application using the Embrac
 ##  Setting up the Crash Reporter
 
 :::info
-See our [FAQ](/android/faq#crashes-and-anrs/) for details on compatibility with other crash reporters.
+See our [FAQ](/android/faq#crashes-and-anrs) for details on compatibility with other crash reporters.
 :::
 
 The Embrace SDK will automatically capture crash reports, assuming you've initialized the Embrace SDK in the [Session Reporting](/android/integration/session-reporting/) guide.