chore: Updates link and names section

src/content/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx

@@ -39,7 +39,7 @@ To forward your Kubernetes logs to New Relic with our plugin:
 
 <InstallFeedback />
 
-## Troubleshoot your Kubernetes plugin for log forwarding installation
+## Troubleshoot your Kubernetes plugin for log forwarding installation [#troubleshoot-installation]
 
 Sometimes, despite correctly installing the Kubernetes plugin for log forwarding (`newrelic-logging` [Helm chart](https://github.com/newrelic/helm-charts/blob/master/charts/newrelic-logging)), you may encounter performance issues that affect the correct delivery of logs. In such circumstances, it can be helpful to look at the log forwarder internal metrics to understand what is the cause of a potential bottleneck.
 
@@ -56,7 +56,7 @@ To configure your Kubernetes cluster to send the log forwarder internal metrics
     Only enable the `newrelic-logging.fluentBit.sendMetrics` when troubleshooting a Kubernetes cluster. We recommend enabling it for a single Kubernetes cluster at a time to ease troubleshooting.
   </Callout>
 
-2. Download this dashboard template file. Open it in a text editor and replace all the `YOUR_ACCOUNT_ID` occurrences (49 in total) by your [New Relic Account ID](/docs/accounts/accounts-billing/account-structure/account-id/).
+2. Download [this dashboard template file](https://raw.githubusercontent.com/newrelic/helm-charts/master/charts/newrelic-logging/fluent-bit-and-plugin-metrics-dashboard-template.json). Open it in a text editor and replace all the `YOUR_ACCOUNT_ID` occurrences (49 in total) by your [New Relic Account ID](/docs/accounts/accounts-billing/account-structure/account-id/).
 
 3. Import the resulting dashboard in JSON format by following [these instructions](/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data/#import-json).