doc: improve authentication guide

docs/content/1.guide/guides/1.debugging.md

@@ -3,8 +3,7 @@ title: Debugging
 description: Steps to take when you need to debug Unlighthouse.
 ---
 
-
-Unlighthouse is built with many edge-cases in mind, but can't always account for every website. 
+Unlighthouse is built with many edge-cases in mind, but can't always account for every website.
 
 ## Enable debugging logs
 

docs/content/1.guide/guides/authentication.md

@@ -148,19 +148,36 @@ export default {
 }
 ```
 
+## Persisting Authentication
+
+If you need to persist your authentication data and it's not working as expected, you can configure Unlighthouse as follows:
+
+```ts [unlighthouse.config.ts]
+export default {
+  // show the browser window
+  puppeteerOptions: {
+    userDataDir: './.puppeteer_data',
+  },
+  lighthouseOptions: {
+    disableStorageReset: true,
+    skipAboutBlank: true,
+  },
+}
+```
+
 ## Troubleshooting
 
 If you're having trouble authenticating,
 you can use the `debug: true` and `headless: false`,
 flags to see what's happening.
 
-```bash
-// unlighthouse.config.ts
+```ts [unlighthouse.config.ts]
 export default {
   debug: true,
   // show the browser window
   puppeteerOptions: {
     headless: false,
+    slowMo: 100,
   },
   // only run a single scan at a time
   puppeteerClusterOptions: {

docs/content/1.guide/guides/chrome-dependency.md

@@ -10,7 +10,7 @@ As a fallback, it will download a Chromium binary for you.
 
 ## Disabling system Chrome
 
-You can disable the system chrome usage by modifying the `chrome.useSystem` flag. 
+You can disable the system chrome usage by modifying the `chrome.useSystem` flag.
 
 This will make Unlighthouse download and use the latest Chrome binary instead.