chore(sweep): Broken links

src/content/docs/apis/nerdgraph/examples/provisions-your-subscriptions-nerdgraph.mdx

@@ -562,7 +562,7 @@ With each account creation call, you must supply at least one New Relic product
     id="mapping-browser"
     title="Browser"
   >
-    [New Relic Browser’s pricing structure](http://newrelic.com/browser-monitoring/pricing) allows an unlimited number of app users, regardless of subscription level. However, the number of allowable page views per month and the data retention period vary by subscription level. For example:
+    New Relic Browser’s pricing structure allows an unlimited number of app users, regardless of subscription level. However, the number of allowable page views per month and the data retention period vary by subscription level. For example:
 
     * Lite accounts include an unlimited number of page views per month and 24-hour data retention.
     * Pro account pricing starts at 500,000 page views per month and three months data retention.

src/content/docs/browser/new-relic-browser/performance-quality/security-browser-monitoring.mdx

@@ -22,7 +22,7 @@ For more information about New Relic's security measures, see our [security and
 
 ## Reported data [#data]
 
-Browser reports many different types of data to help you analyze your website's performance. It <DNT>**only**</DNT> reports page view data, unless you have subscribed to [Pro features](http://newrelic.com/browser-monitoring/pricing). You can also [enable functionality](/docs/browser/new-relic-browser/welcome-new-relic-browser/new-relic-browser#enhanced-features) for AJAX requests, JavaScript errors, and session traces.
+Browser reports many different types of data to help you analyze your website's performance. It only reports page view data, unless you have subscribed to Pro features. You can also [enable functionality](/docs/browser/new-relic-browser/welcome-new-relic-browser/new-relic-browser#enhanced-features) for AJAX requests, JavaScript errors, and session traces.
 
 For most data types, browser [transmits the data securely](/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-page-load-timing#transmission) using HTTPS encryption. The browser agent transmits data to New Relic's [collectors](/docs/accounts-partnerships/getting-started-new-relic/glossary#collector) by using either of the domains `bam.nr-data.net` or `bam-cell.nr-data.net`.
 

src/content/docs/release-notes/agent-release-notes/python-release-notes/python-agent-2202.mdx

@@ -20,7 +20,7 @@ For a list of known issues with the Python agent see our online help article on
 ### New Features:
 
 * Use of HTTP proxies over SSL using the HTTP CONNECT tunnelling mechanism is now supported. Set the 'proxy_scheme' to 'http' to invoke this mode. This will become the default in a future version of the agent. If migrating from an older agent version and need to keep the existing behaviour going forward, set 'proxy_scheme' to 'https'. Alternatively, ensure you provide the scheme in the form of a URI as part of the 'proxy_host' setting.
-* Added request queueing support to the instrumentation for the Tornado ASYNC framework. Request queueing times should start showing in the APM Overview page when a frontend web server such as Nginx, has been configured to add the appropriate headers. For more details see our documentation on setting up [tracking of queueing time](http://newrelic.com/docs/features/request-queuing-and-tracking-frontend-time).
+* Added request queueing support to the instrumentation for the Tornado ASYNC framework. Request queueing times should start showing in the APM Overview page when a frontend web server such as Nginx, has been configured to add the appropriate headers. 
 * The 'newrelic.agent.record_exception()' can now be called without actually passing it any exception details. In this case, the details of any current exception being handled will be used instead.
 * Added a new mechanism for automatic discovery of third party instrumentation modules as an alternative to having to list them explicitly in the agent configuration file. Any such instrumentation module should register entry points under the 'newrelic.hooks' group in 'setup.py' for that package. The entries should be of the form 'target-module = instrumentation-module:function'. When the 'target-module' is imported, the function 'instrumentation-module:function' will be executed and passed the module. Any instrumentation module should then use functions provided by our agent API under 'newrelic.agent' to instrument the module as necessary.
 

src/content/docs/style-guide/writing-docs/writer-workflow/tech-writer-workflow.mdx

@@ -93,7 +93,7 @@ You only need to rebuild the local site when it crashes, not after every save or
    * `cd ~/Documents/github/docs-website`
 2. Run yarn with the following commands: `yarn && yarn start`
 3. The site will take a few minutes to build. Make yourself some tea or coffee.
-4. Once built, preview the site in your browser by navigating to [http://localhost:8000/](http://localhost:8000/)
+4. Once built, preview the site in your browser by navigating to `http://localhost:8000/`
 
 ## 4. Publish your commits [#publish-commits]