links fix

Author: daisyfaithauma

src/content/docs/browser-rendering/how-to/pdf-generation.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { Aside, WranglerConfig } from "~/components";
 
-As seen in the [Getting Started guide](/browser-rendering/get-started/screenshots/), Browser Rendering can be used to generate screenshots for any given URL. Alongside screenshots, you can also generate full PDF documents for a given webpage, and can also provide the webpage markup and style ourselves.
+As seen in the [Getting Started guide](/browser-rendering/workers-binding-api/screenshots/), Browser Rendering can be used to generate screenshots for any given URL. Alongside screenshots, you can also generate full PDF documents for a given webpage, and can also provide the webpage markup and style ourselves.
 
 ## Prerequisites
 
@@ -26,9 +26,8 @@ npm install @cloudflare/puppeteer --save-dev
 3. Add your Browser Rendering binding to your new Wrangler configuration:
 
 <WranglerConfig>
-```toml
-browser = { binding = "BROWSER" }
-```
+	```toml browser = {(binding = "BROWSER")}
+	```
 </WranglerConfig>
 
 4. Replace the contents of `src/index.ts` (or `src/index.js` for JavaScript projects) with the following skeleton script:

src/content/docs/browser-rendering/platform/puppeteer.mdx

@@ -67,7 +67,7 @@ This script [launches](https://pptr.dev/api/puppeteer.puppeteernode.launch) the
 
 ### Keep Alive
 
-If users omit the `browser.close()` statement, it will stay open, ready to be connected to again and [re-used](/browser-rendering/get-started/reuse-sessions/) but it will, by default, close automatically after 1 minute of inactivity. Users can optionally extend this idle time up to 10 minutes, by using the `keep_alive` option, set in milliseconds:
+If users omit the `browser.close()` statement, it will stay open, ready to be connected to again and [re-used](/browser-rendering/workers-binding-api/reuse-sessions/) but it will, by default, close automatically after 1 minute of inactivity. Users can optionally extend this idle time up to 10 minutes, by using the `keep_alive` option, set in milliseconds:
 
 ```js
 const browser = await puppeteer.launch(env.MYBROWSER, { keep_alive: 600000 });

src/content/docs/browser-rendering/workers-binding-api/reuse-sessions.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { Render, PackageManagers, WranglerConfig } from "~/components";
 
-The best way to improve the performance of your browser rendering worker is to reuse sessions. One way to do that is via [Durable Objects](/browser-rendering/get-started/browser-rendering-with-do/), which allows you to keep a long running connection from a worker to a browser. Another way is to keep the browser open after you've finished with it, and connect to that session each time you have a new request.
+The best way to improve the performance of your browser rendering worker is to reuse sessions. One way to do that is via [Durable Objects](/browser-rendering/workers-binding-api/browser-rendering-with-do/), which allows you to keep a long running connection from a worker to a browser. Another way is to keep the browser open after you've finished with it, and connect to that session each time you have a new request.
 
 In short, this entails using `browser.disconnect()` instead of `browser.close()`, and, if there are available sessions, using `puppeteer.connect(env.MY_BROWSER, sessionID)` instead of launching a new browser session.
 
@@ -51,7 +51,8 @@ compatibility_date = "2023-03-14"
 compatibility_flags = [ "nodejs_compat" ]
 
 browser = { binding = "MYBROWSER" }
-```
+
+````
 </WranglerConfig>
 
 ## 4. Code
@@ -133,7 +134,7 @@ export default {
 		return sessionId!;
 	},
 };
-```
+````
 
 Besides `puppeteer.sessions()`, we've added other methods to facilitate [Session Management](/browser-rendering/platform/puppeteer/#session-management).