fix last Linkcheker 404s (#3705)

documentation/docs/admin/security/ssl_encryption.md

@@ -1,14 +1,15 @@
 # SSL encryption
 
 Valid and trusted SSL certificates are needed to encrypt traffic between the client and server.  Certificates can be purchased online from various sources, or some organizations generate their own trusted certificates.  Regardless of which path you choose for enabling maximum security, the process to secure PMM consists of the following components:
+{.power-number}
 
 1. Staging the files in the proper locations:
 
     - You can [directly mount](#mounting-certificates) to a local directory containing the required certificates or
     - You can [copy the files](#copying-certificates) to the appropriate directory in your Container|AMI|OVF
 
-2. Restarting PMM
-3. Ensuring the client(s) trust the certificate issuer ([Ubuntu](https://ubuntu.com/server/docs/security-trust-store) | [RedHat](https://www.redhat.com/sysadmin/configure-ca-trust-list) can get you started but this is somewhat OS specific)
+2. Restarting PMM.
+3. Ensuring the Clients trust the certificate issuer ([Ubuntu](https://ubuntu.com/server/docs/install-a-root-ca-certificate-in-the-trust-store) | [RedHat](https://www.redhat.com/sysadmin/configure-ca-trust-list) can get you started but this is somewhat OS specific)
 
 
 With our Docker, OVF and AMI images, certificates are stored in `/srv/nginx` and our self-signed certificates are staged there by default.

documentation/docs/index.md

@@ -1,6 +1,5 @@
 # About PMM
 
-
 <i info>:material-information: Info:</i> This is the documentation for the latest PMM release. For details, see the [PMM {{release}} release notes](release-notes/3.0.0.md) and the [3.0.0-1 update](release-notes/3.0.0_1.md).  
 
 

documentation/docs/install-pmm/install-pmm-client/docker.md

@@ -12,9 +12,9 @@ The PMM Client Docker image is available for both x86_64 and ARM64 architectures
     ```
 
 2. Create a Docker volume to store persistent data:
-+    ```sh
-+    docker volume create pmm-client-data
-+    ```
+   ```sh
+    docker volume create pmm-client-data
+   ```
 
 3. Execute the following command to start the [pmm-agent](../../use/commands/pmm-agent.md) in Setup mode. Replace `X.X.X.X` with the IP address of your PMM Server:
 
@@ -36,23 +36,20 @@ The PMM Client Docker image is available for both x86_64 and ARM64 architectures
        - Do not use the `docker --detach` option with Docker, as the pmm-agent logs output directly to the console, and detaching the container will prevent you from seeing these logs:
       - You can find a complete list of compatible environment variables [here](../../use/commands/pmm-agent.md).
 
-3. Check status:
-
+3. Run the following command to verify the PMM client status. You should also see an increase in the number of monitored nodes in the PMM user interface:
     ```sh
       docker exec -t pmm-client pmm-admin status
     ```
 
-    In the PMM user interface you will also see an increase in the number of monitored nodes.
-
 You can now add services with [`pmm-admin`](../../use/commands/pmm-admin.md) by prefixing commands with `docker exec pmm-client`.
 
 !!! hint alert alert-success "Tips for Docker configuration"
 
-   - Firewall and routing rules: Ensure your host's firewall and routing rules are configured to allow Docker communications. This is crucial for Docker containers to communicate properly. For more details, see to the [troubleshooting checklist](https://chat.deepseek.com/a/troubleshoot/checklist.md).
+   - Firewall and routing rules: Ensure your host's firewall and routing rules are configured to allow Docker communications. This is crucial for Docker containers to communicate properly. For more details, see to the [troubleshooting checklist](../../troubleshoot/checklist.md).
 
    - Help command: If you need assistance with PMM Client, you can run the following command to display help information: `docker run --rm percona/pmm-client:3 --help`.
 
-How to view your monitored node
+View your monitored node:
 {.power-number}
 
     1. Go to the main menu and select **Operating System (OS) > Overview**.