chore: rename pages and add aliases

.eslintignore

@@ -3,6 +3,7 @@ public/
 node_modules/
 docs/sources/get-started/run-cloud-tests-from-the-CLI.md
 docs/sources/get-started/run-your-first-tests.md
+/docs/sources/next/testing-guides/injecting-faults-with-xk6-disruptor/expose-your-application.md
 CONTRIBUTING_FILE_FORMAT.md
 src/data/markdown/docs/40 xk6-disruptor/01 Get started/01 First steps.md
 src/data/markdown/docs/40 xk6-disruptor/01 Get started/04 Expose Your Application.md

docs/sources/next/testing-guides/injecting-faults-with-xk6-disruptor/expose--your-application.md → docs/sources/next/testing-guides/injecting-faults-with-xk6-disruptor/expose-your-application.md

@@ -2,6 +2,8 @@
 title: 'Expose your application'
 excerpt: 'How to make your applications accessible from the test scripts.'
 weight: 04
+aliases:
+  - ./expose--your-application/
 ---
 
 # Expose your application
@@ -31,7 +33,7 @@ Until this issue is solved in `kubectl`, tests using port forwarding to access a
 
 The simplest way to accomplish this is to ensure the scenario that executes the load (#2) starts after the scenario that injects the faults (#1):
 
-```javascript
+```js
     scenarios: {
         disrupt: {   // #1 inject faults
             executor: 'shared-iterations',
@@ -62,25 +64,29 @@ If your cluster is deployed in a public cloud, check your cloud provider documen
 If the service that you want your tests to access is not defined as a load balancer, you can change the service type with the following command. The service will then receive an external IP.
 
 {{< code >}}
+
 ```bash
 kubectl -n <name space> patch svc <service name> -p '{"spec": {"type": "LoadBalancer"}}'
 ```
 
 ```windows-powershell
 kubectl -n <name space> patch svc <service name> -p '{\"spec\": {\"type\": \"LoadBalancer\"}}'
 ```
+
 {{< /code >}}
 
 You can retrieve the external IP address and store it in an environment variable (`SVC_IP` in this example) using the following command:
 
 {{< code >}}
+
 ```bash
 SVC_IP=$(kubectl -n <name space>  get svc <service name> --output jsonpath='{.status.loadBalancer.ingress[0].ip}')
 ```
 
 ```windows-powershell
 $Env:SVC_IP=$(kubectl -n <name space>  get svc <service name> --output jsonpath='{.status.loadBalancer.ingress[0].ip}')
 ```
+
 {{< /code >}}
 
 ### Configuring a LoadBalancer in Kind

docs/sources/next/testing-guides/injecting-faults-with-xk6-disruptor/how--it-works.md → docs/sources/next/testing-guides/injecting-faults-with-xk6-disruptor/how-it-works.md

@@ -2,6 +2,8 @@
 title: 'How xk6-disruptor works'
 excerpt: 'A brief description of the components of the xk6-disruptor and how they work when inject faults in a target system.'
 weight: 05
+aliases:
+  - ./how--it-works/
 ---
 
 # How xk6-disruptor works

docs/sources/next/using-k6/protocols/ssl-tls/online-certificate-status-protocol--ocsp.md → docs/sources/next/using-k6/protocols/ssl-tls/online-certificate-status-protocol-ocsp.md

@@ -2,6 +2,8 @@
 title: 'Online Certificate Status Protocol (OCSP)'
 excerpt: 'k6 supports OCSP stapling, receiving and parsing a stapled response as part of
 the TLS connection setup.'
+aliases:
+  - ./online-certificate-status-protocol--ocsp/
 ---
 
 ## What is OCSP?