Update README.md

README.md

@@ -61,4 +61,4 @@ I'm using multiple methods of reporting here. Reporting tasks are done in a [sep
 Upon a pull request being closed, the Tesults branch target is deleted via the same script with another [Github Actions job](https://github.com/angelo-loria/playwright-boilerplate/blob/main/feat/acme-store-refactor/.github/workflows/delete-tesults-target.yml). This is done to keep the number of targets in Tesults to a minimum on my free account. 
 
 ### Lighthouse
-I'm using the [Google Lighthouse](https://developers.google.com/web/tools/lighthouse) NPM package for performance and additional accessibility testing. The test setup and execution is a bit unique tests so I've separated them into their own spec file, they use a unique config file, and they are uploaded to Tesults separately from the other tests. [See the directory here](https://github.com/angelo-loria/playwright-boilerplate/tree/main/tests/lighthouse). I've added a specific script in the [package.json](https://github.com/angelo-loria/playwright-boilerplate/blob/main/package.json) file for executing these tests with their specific config file and running the [tesults-lighthouse.js](https://github.com/angelo-loria/playwright-boilerplate/blob/main/.scripts/tesults-lighthouse.js) script afterwards. The script uses the Tesults npm package to upload the results to Tesults to a specific target that's set up with the results interpretation feature to display the individual Lighthouse scores for each page. [It looks pretty slick](https://www.tesults.com/results/rsp/view/results/target/48242328-a7eb-4ab4-8065-3a3686634e5c-1701748288944). Tesults is hosting the Lighthouse HTML reports and they're uploaded as artifacts to Github Actions as well. [Here's what one of those reports looks like.](https://www.tesults.com/results/files/pdl30/48242328-a7eb-4ab4-8065-3a3686634e5c-1701748288944-1701750294894-0/0/about.html)
+I'm using the [Google Lighthouse](https://developers.google.com/web/tools/lighthouse) NPM package for performance and additional accessibility testing. The test setup and execution is a bit unique tests so I've separated them into their own spec file, they use a unique config file, and they are uploaded to Tesults separately from the other tests. [See the directory here](https://github.com/angelo-loria/playwright-boilerplate/tree/main/tests/lighthouse). I've added a specific script in the [package.json](https://github.com/angelo-loria/playwright-boilerplate/blob/main/package.json) file for executing these tests with their specific config file and running the [tesults-lighthouse.js](https://github.com/angelo-loria/playwright-boilerplate/blob/main/.scripts/tesults-lighthouse.js) script afterwards. The script uses the Tesults npm package to upload the results to Tesults to a specific target that's set up with the results interpretation feature to display the individual Lighthouse scores for each page. [It looks pretty slick](https://www.tesults.com/angelo-loria/acme-store-demo/lighthouse). Tesults is hosting the Lighthouse HTML reports and they're uploaded as artifacts to Github Actions as well. [Here's what one of those reports looks like.](https://www.tesults.com/results/files/pdl30/48242328-a7eb-4ab4-8065-3a3686634e5c-1701748288944-1701750294894-0/0/about.html)