[docs] Remove trailing spaces from all doc sources.

Double trailing space in Markdown creates a line break `<br>` in HTML.
That's never intended in the docs.

Signed-off-by: Nick Volynkin <nick.volynkin@gmail.com>

Author: NickVolynkin

content/en/blog/2024-04-05-diy-create-your-own-cloud-with-kubernetes-part-1/index.md

@@ -89,7 +89,7 @@ update and maintain.
 Judge for yourself: in the cloud, to update a node, you typically delete the virtual machine
 (or even use `kubectl delete node`) and you let your node management tooling create a new
 one, based on an immutable image. The new node will join the cluster and ”just work” as a  node;
-following a very simple and commonly used pattern in the Kubernetes world. 
+following a very simple and commonly used pattern in the Kubernetes world.
 Many clusters order new virtual machines every few minutes, simply because they can use
 cheaper spot instances. However, when you have a physical server, you can't just delete and
 recreate it, firstly because it often runs some cluster services, stores data, and its update process
@@ -155,7 +155,7 @@ output:
 Then we use the `docker` command line tool to build an OS image:
 
 ```
-cat config.yaml | docker run --rm -i -v /dev:/dev --privileged "ghcr.io/siderolabs/imager:v1.6.4" - 
+cat config.yaml | docker run --rm -i -v /dev:/dev --privileged "ghcr.io/siderolabs/imager:v1.6.4" -
 ```
 
 And as a result, we get a Docker container image with everything we need, which we can use to

content/en/docs/_index.md

@@ -14,4 +14,4 @@ Cozystack is a free PaaS platform and framework for building clouds
 
 With Cozystack, you can transform your bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
 
-You can use Cozystack to build your own cloud or to provide a cost-effective development environments.  
+You can use Cozystack to build your own cloud or to provide a cost-effective development environments.

content/en/docs/development/development.md

@@ -164,7 +164,7 @@ make update                       # Download new version from upstream
 make image                        # Build cilium image
 git diff .                        # Show diff with changed manifests
 make diff                         # Show diff with applied cluster manifests
-make apply                        # Apply changed manifests to the cluster 
+make apply                        # Apply changed manifests to the cluster
 kubectl get pod -n cozy-cilium    # Check if everything works as expected
 git commit -m "Update cilium"     # Commit changes to the branch
 ```

content/en/docs/getting-started/create-tenant.md

@@ -33,7 +33,7 @@ See the [OIDC guide]({{% ref "/docs/operations/oidc" %}}) for details on how to
 
 ## Create a Tenant
 
-Tenants are created using the Cozystack application named `Tenant`. 
+Tenants are created using the Cozystack application named `Tenant`.
 After installation, Cozystack includes a built-in tenant called `tenant-root`.
 This root tenant is reserved for platform administrators and should only be used to create child tenants.
 Although it’s technically possible to install applications in `tenant-root`,
@@ -153,5 +153,5 @@ In general, administrators do **not** need to retrieve kubeconfig files for nest
 These clusters are installed by the tenant user, within their own tenant namespace.
 Tenant users have full control over their nested Kubernetes environments.
 
-To access a nested Kubernetes cluster, the tenant user can download the kubeconfig file 
+To access a nested Kubernetes cluster, the tenant user can download the kubeconfig file
 directly from the corresponding application's page in the dashboard.

content/en/docs/getting-started/deploy-app.md

@@ -16,9 +16,9 @@ You’ll learn how to:
 -   Create a managed Kubernetes cluster, configure DNS, and access the cluster.
 -   Deploy a containerized application to the new cluster.
 
-You don’t need in-depth Kubernetes knowledge to complete this tutorial—most steps are done through the Cozystack web interface.  
+You don’t need in-depth Kubernetes knowledge to complete this tutorial—most steps are done through the Cozystack web interface.
 
-This is your fast track to a successful first deployment on Cozystack.  
+This is your fast track to a successful first deployment on Cozystack.
 Once you're done, you’ll have a working setup ready for your own applications—and a solid foundation to build upon and showcase to your team.
 
 ## Prerequisites
@@ -34,9 +34,9 @@ Before you begin:
 -   **DNS for dev/testing:** To access the deployed app over HTTPS you need a DNS record set up.
     A wildcard DNS record is preferred, as it's more convenient to use.
 
-> 🛠️ **CLI is optional.** 
-> You don’t need to use `kubectl` or `helm` unless you want to. 
-> All major steps (like creating the Kubernetes cluster and managed services) can be done entirely in the Cozystack Dashboard. 
+> 🛠️ **CLI is optional.**
+> You don’t need to use `kubectl` or `helm` unless you want to.
+> All major steps (like creating the Kubernetes cluster and managed services) can be done entirely in the Cozystack Dashboard.
 > The only point where you’ll need the CLI is when deploying the app to a Kubernetes cluster.
 
 ## 1. Access the Cozystack Dashboard
@@ -53,10 +53,10 @@ Choose your login method below:
 
 {{< tabs name="access_dashboard" >}}
 {{% tab name="OIDC" %}}
-Click the `OIDC Login` button.  
+Click the `OIDC Login` button.
 This will take you to the Keycloak login page.
 
-Enter your credentials and click `Login`.  
+Enter your credentials and click `Login`.
 If everything is configured correctly, you'll be logged in and redirected back to the dashboard.
 {{% /tab %}}
 
@@ -78,17 +78,17 @@ As a tenant user, you can’t install or modify them, but your own apps will run
 
 ## 2. Create a Managed PostgreSQL
 
-Cozystack lets you provision managed databases directly on the hardware layer for maximum performance.  
+Cozystack lets you provision managed databases directly on the hardware layer for maximum performance.
 Each database is created inside your tenant namespace and is automatically accessible from your nested Kubernetes cluster.
 
-If you're familiar with services like AWS RDS or GCP Cloud SQL, the experience is similar—  
+If you're familiar with services like AWS RDS or GCP Cloud SQL, the experience is similar—
 except it's fully integrated with Cozystack and isolated within your own tenant.
 
 > Throughout this tutorial, you’ll have the option to use either the Cozystack dashboard (UI) or `kubectl`:
 >
 > -   **Cozystack Dashboard** offers the quickest and most straightforward experience—recommended if this is your first time using Cozystack.
 > -   **`kubectl`** provides in-depth visibility into how managed services are deployed behind the scenes.
-> 
+>
 > While neither approach reflects how services are typically deployed in production,
 > both are well-suited for learning and experimentation—making them ideal for this tutorial.
 
@@ -161,7 +161,7 @@ kubectl apply -f postgres.yaml
 
 ### 2.2 Get the Connection Credentials
 
-Navigate to the **Applications** tab, then find and open the `instaphoto-postgres` application.  
+Navigate to the **Applications** tab, then find and open the `instaphoto-postgres` application.
 Once the application is installed and ready, you’ll find connection details in the **Application Resources** section of the dashboard.
 
 -   The **Secrets** tab contains the database password for each user you defined.
@@ -178,7 +178,7 @@ This will create a service named `postgres-<name>-external-write` with a public
 
 ## 3. Create a Cache Service
 
-From this point on, you'll use your tenant credentials to access the platform.  
+From this point on, you'll use your tenant credentials to access the platform.
 Use the tenant's kubeconfig for `kubectl`, and the token from it to access the dashboard.
 
 {{< tabs name="create_redis" >}}
@@ -228,7 +228,7 @@ kubectl apply -f redis.yaml
 {{% /tab %}}
 {{< /tabs >}}
 
-After a short time, the Redis application will be installed in the `team1` tenant.  
+After a short time, the Redis application will be installed in the `team1` tenant.
 The generated password can be found in the dashboard.
 
 {{< tabs name="redis_password" >}}
@@ -254,19 +254,19 @@ kubectl -n tenant-team1 get secret redis-instaphoto-auth
 
 ## 4. Deploy a Nested Kubernetes Cluster
 
-The nested Kubernetes cluster is created in the same way as the database and cache. 
+The nested Kubernetes cluster is created in the same way as the database and cache.
 However, there are a few important additional points to consider:
 
 -   **`etcd` must be enabled in the tenant**<br/>
     The `etcd` service is required to run a nested Kubernetes cluster and can only be enabled by a Cozystack administrator.
--   **Verify your quota.**<br/>  
+-   **Verify your quota.**<br/>
     Ensure your tenant has enough CPU, RAM, and disk resources to create and run a cluster.
--   **Choose an appropriate instance preset.**<br/>  
-    Avoid selecting presets that are too small. A Kubernetes node consumes approximately 2.5 GB of RAM just for system components.  
-    For example, if you select a 4 GB RAM preset, only about 1.5 GB will be available for your actual workloads.  
+-   **Choose an appropriate instance preset.**<br/>
+    Avoid selecting presets that are too small. A Kubernetes node consumes approximately 2.5 GB of RAM just for system components.
+    For example, if you select a 4 GB RAM preset, only about 1.5 GB will be available for your actual workloads.
     4 GB is sufficient for testing, but in general, it’s better to provision **fewer nodes with more RAM** than many nodes with minimal RAM.
--   **Enable `ingress` and `cert-manager` if needed.**<br/>  
-    If you're deploying web applications, you will likely need ingress and certificate management.  
+-   **Enable `ingress` and `cert-manager` if needed.**<br/>
+    If you're deploying web applications, you will likely need ingress and certificate management.
     Both can be enabled with a checkbox when configuring the nested Kubernetes application in Cozystack.
 
 Once the nested Kubernetes cluster is ready, you'll find its kubeconfig files in the **Secrets** tab of the application page in the dashboard.
@@ -327,8 +327,8 @@ To deploy your application:
 1.  Run a standard Helm deployment command, for example:
 
     ```bash
-    helm upgrade --install <release-name> <chart-path> -f values.yaml                          
+    helm upgrade --install <release-name> <chart-path> -f values.yaml
     ```
-    
+
 Service names such as the database and cache do not need DNS suffixes.
 They are accessible within the same namespace by their service names.

content/en/docs/getting-started/first-deployment.md

@@ -34,7 +34,7 @@ It will guide you through the following steps:
 1.  Configure storage
 1.  Configure networking
 1.  Deploy etcd, ingress and monitoring stack
-1.  Finalize deployment and access Cozystack dashboard 
+1.  Finalize deployment and access Cozystack dashboard
 
 
 ## 1. Create Kubernetes cluster
@@ -104,7 +104,7 @@ Installing Cozystack starts with choosing a Cozystack bundle.
 In this tutorial, we'll use the complete `paas-full` bundle, made for installing on bare metal and including everything
 Cozystack has to offer.
 
-### 2.1. Prepare Configuration File 
+### 2.1. Prepare Configuration File
 
 Take the configuration example below and fill in the values according to your network setup.
 Make sure to use the same value in `patch.yaml` and `patch-controlplane.yaml` files.
@@ -514,7 +514,7 @@ kubectl patch cm -n cozy-system cozystack --type merge -p='{"data":{
 {{% /alert %}}
 
 Use `dashboard.example.org` to access the system dashboard, where `example.org` is your domain specified for `tenant-root`.
-In this example, `dashboard.example.org` is located at 192.168.100.200. 
+In this example, `dashboard.example.org` is located at 192.168.100.200.
 
 Get authentication token from `tenant-root`:
 ```bash
@@ -524,7 +524,7 @@ kubectl get secret -n tenant-root tenant-root -o go-template='{{ printf "%s\n" (
 ### 6.3 Access metrics in Grafana
 
 Use `grafana.example.org` to access the system monitoring, where `example.org` is your domain specified for `tenant-root`.
-In this example, `grafana.example.org` is located at 192.168.100.200. 
+In this example, `grafana.example.org` is located at 192.168.100.200.
 
 - login: `admin`
 - request a password:

content/en/docs/getting-started/hardware-requirements.md

@@ -41,7 +41,7 @@ Understanding each role ensures the stability and scalability of your environmen
 
 - **Primary Disk**: This disk contains the Talos Linux operating system, essential system kernel modules and
   Cozystack system base pods, logs, and base container images.
-  
+
   Minimum: 32 GB; approximately 26 GB is used in a standard Cozystack setup.
   The Talos installation expects `/dev/sda` as the system disk (virtio drives usually appear as `/dev/vda`).
 
@@ -110,4 +110,4 @@ Achieving high availability adds to the basic production environment requirement
 - Expect a significant amount of horizontal, inter-node traffic inside clusters.
   It is usually caused by multiple replicas of services and databases deployed across different nodes exchanging data.
   Also, virtual machines with live migration require replicated volumes, which further increases the amount of traffic.
-  
+

content/en/docs/guides/applications.md

@@ -35,10 +35,10 @@ Deployment involves the following components:
     of Kubernetes control planes as pods within a root cluster.
     Each control plane pod includes essential components like `kube-apiserver`, `controller-manager`, and `scheduler`,
     allowing for efficient multi-tenancy and resource utilization.
-  
+
 -   **Etcd Cluster**: A dedicated etcd cluster is deployed using Ænix's [aenix-io/etcd-operator](https://github.com/aenix-io/etcd-operator).
     It provides reliable and scalable key-value storage for the Kubernetes control plane.
-  
+
 -   **Worker Nodes**: Virtual Machines are provisioned to serve as worker nodes.
     These nodes are configured to join the tenant Kubernetes cluster, enabling the deployment and management of workloads.
 

content/en/docs/guides/bundles/_index.md

@@ -137,7 +137,7 @@ It includes three optional components:
 
 ## Learn More
 
-To see the full list of components and configuration options for each bundle, refer to the 
+To see the full list of components and configuration options for each bundle, refer to the
 [bundle reference documentation]({{% ref "/docs/operations/bundles" %}}).
 
 To deploy a selected bundle, follow the [Cozystack quickstart guide]({{% ref "/docs/getting-started/first-deployment" %}}) or platform installation documentation.

content/en/docs/guides/concepts.md

@@ -21,10 +21,10 @@ Once access is granted to the tenant Kubernetes, the user can order physical vol
 
 All use cases are presented here:
 
-* [**Using Cozystack to build public cloud**](/docs/guides/use-cases/public-cloud/)  
+* [**Using Cozystack to build public cloud**](/docs/guides/use-cases/public-cloud/)
   How to use Cozystack to build public cloud
 
-* [**Using Cozystack to build private cloud**](/docs/guides/use-cases/private-cloud/)  
+* [**Using Cozystack to build private cloud**](/docs/guides/use-cases/private-cloud/)
   How to use Cozystack to build private cloud
 
 * [**Using Cozystack as Kubernetes distribution**](/docs/guides/use-cases/kubernetes-distribution/)