fix: update broken links

Author: mdcruz

src/data/markdown/translated-guides/en/08 Testing Guides/03 Load testing websites.md

@@ -172,7 +172,7 @@ For example, a browser-based load testing script might include instructions to n
 Unlike protocol-based load testing, browser-based load testing scripts generate load by starting multiple instances of browsers and interacting with your application the way real users would. Testing at the browser level can also be the only option for testing Single-Page Applications where a lot of the application logic is executed by client-side scripts.
 
 Scripting on the browser level usually requires the use of different tools from the ones used to test at the protocol level.
-However, k6 now has an experimental module called [k6 browser](https://k6.io/docs/using-k6-browser/overview/) that allows the creation of browser-based test scripts alongside protocol-based ones.
+However, k6 now has an experimental module called [k6 browser](/using-k6-browser/overview/) that allows the creation of browser-based test scripts alongside protocol-based ones.
 
 #### Sample browser-based test script
 
@@ -226,9 +226,9 @@ The following steps can help you get started with a browser-level test script.
 
 **Identify unique selectors.** Once you have identified which page elements a user interacts with, use the Element Inspector for DevTools in your browser to find a unique, static, and simple way to identify each element. The script needs selectors to find the right element to interact with.
 
-**Use elements to verify responses.** After every action, use [locators](https://k6.io/docs/javascript-api/k6-experimental/browser/locator/) to search for elements on the page that you would expect to find. This verification helps ensure that the script has reached the expected page.
+**Use elements to verify responses.** After every action, use [locators](/javascript-api/k6-experimental/browser/locator/) to search for elements on the page that you would expect to find. This verification helps ensure that the script has reached the expected page.
 
-**Take screenshots for every action while debugging.** One of the advantages of browser-based testing is the ability to take screenshots. After every user interaction the script simulates, use [page.screenshot](https://k6.io/docs/javascript-api/k6-experimental/browser/page/) to save a visual image of what the script encountered for later troubleshooting.
+**Take screenshots for every action while debugging.** One of the advantages of browser-based testing is the ability to take screenshots. After every user interaction the script simulates, use [page.screenshot](/javascript-api/k6-experimental/browser/page/) to save a visual image of what the script encountered for later troubleshooting.
 
 
 ### Hybrid load testing