Update troubleshooting.md

updating debug logging link

Author: paulbarkman

src/connections/sources/catalog/libraries/mobile/android/troubleshooting.md

@@ -10,7 +10,7 @@ strat: android
     - The `writekey` might change when you make changes to the source from the Segment web app.
     - If the `writeKey` you entered is something other than a string or an empty string your app may crash
     - If the `writeKey` you entered is a valid form but not the correct writeKey for your specific source, you won't see an error response. Segment receives the data, but cannot route it to your source (debugger).
-3. [Enable logging](/docs/connections/sources/catalog/libraries/mobile/android/#debugging) to confirm if call is being sent to Segment
+3. [Enable logging](/docs/connections/sources/catalog/libraries/mobile/android/#adding-debug-logging) to confirm if call is being sent to Segment
 
 
 ## No events in my destinations
@@ -29,7 +29,7 @@ If you still don't see data getting to your destination, continue debugging base
 
 Inspect one of your data payloads. If you are using device-mode for a specific destination, the value of that integration should be set to `false` in the `integrations` object. That means that the data is being sent from the device directly to the destination's API endpoints, and not through Segment's servers. This is expected if you chose to use a device-mode destination's SDK with Segment's during installation.
 
-Enable verbose [logging](/docs/connections/sources/catalog/libraries/mobile/android/#debugging) and trigger the call in question. You should see a call to Segment, and one going to the partner SDK.  It will show you exactly which partner method was invoked and the arguments it was invoked with!
+Enable verbose [logging](/docs/connections/sources/catalog/libraries/mobile/android/#adding-debug-logging) and trigger the call in question. You should see a call to Segment, and one going to the partner SDK.  It will show you exactly which partner method was invoked and the arguments it was invoked with!
 
 ## Debugging Cloud-mode Destinations