Autofix: trailing-spaces

Author: autofix-bot

src/blog/moving-software-development-to-the-cloud.md

@@ -15,15 +15,15 @@ We certainly welcome the additional push Codespaces will bring, but it is import
 
 ### Gitpod is Open-Source, Multi-Cloud, and Works With GitLab, GitHub, and Bitbucket
 
-Gitpod is an **open-source platform** which means you get full transparency over how Gitpod works and can even contribute to it. The [vibrant open-source community](https://community.gitpod.io/) of Gitpod welcomes everyone, and empowers them to develop additional features without restrictions. 
+Gitpod is an **open-source platform** which means you get full transparency over how Gitpod works and can even contribute to it. The [vibrant open-source community](https://community.gitpod.io/) of Gitpod welcomes everyone, and empowers them to develop additional features without restrictions.
 
 Furthermore, you can run Gitpod on your own infrastructure and any cloud provider. **Gitpod seamlessly works with GitHub, GitLab and Bitbucket** and can be deployed to public, private or hybrid clouds, neatly integrating into your infrastructure, **giving you full control of your system and your source code**.
 
 ### Gitpod is Powerful
 
-As a highly-optimized Kubernetes application **Gitpod is built on next-gen container technology** instead of VMs. This allows Gitpod to be extremely resource efficient giving you the best 💥 for the 💵 
+As a highly-optimized Kubernetes application **Gitpod is built on next-gen container technology** instead of VMs. This allows Gitpod to be extremely resource efficient giving you the best 💥 for the 💵
 
-Compared to virtual machines, isolating workspace containers from each other is harder. At Gitpod we’ve integrated the latest container isolation mechanisms that securely allow users to benefit from the resource efficiency of containers while still having root privileges. For the user this means full access to `sudo` and `docker` 🐳 Here’s a [great technical presentation](https://youtu.be/l4I2TVAnBuw?t=174) explaining how we make this happen. 
+Compared to virtual machines, isolating workspace containers from each other is harder. At Gitpod we’ve integrated the latest container isolation mechanisms that securely allow users to benefit from the resource efficiency of containers while still having root privileges. For the user this means full access to `sudo` and `docker` 🐳 Here’s a [great technical presentation](https://youtu.be/l4I2TVAnBuw?t=174) explaining how we make this happen.
 
 The result is that Gitpod offers more powerful dev environments with a small ecological footprint. Furthermore, we run Gitpod.io on a 100% carbon-neutral cloud service ❤️🌍
 
@@ -33,7 +33,7 @@ Gitpod is not only extremely fast because of the higher efficiency, but also bec
 
 The metric that matters here is the time it takes until a dev environment is **ready-to-code**. Ready-to-code means that developers can actually start writing code and don’t have to wait for builds, dependencies to download or code generators to run.
 
-With GitHub Codespaces and other solutions whenever you start a new dev environment, you are left with a raw copy of the code. So before you start writing code, you’ll need to run a bunch of processes and wait until they are finished. 
+With GitHub Codespaces and other solutions whenever you start a new dev environment, you are left with a raw copy of the code. So before you start writing code, you’ll need to run a bunch of processes and wait until they are finished.
 
 Instead Gitpod prebuilds dev environments when a new commit is pushed to the remote repository. The following diagram illustrates the idea:
 
@@ -47,11 +47,11 @@ We believe prebuilding dev environments the way Gitpod does it, is key towards [
 
 The real competition is the habit of maintaining stateful environments on overpowered local machines. We welcome GitHub and Microsoft to join forces in convincing developers around the world about the workflow and productivity benefits of automated, cloud-based dev environments 🥰
 
-We are excited about the things we announced yesterday around [Root, Docker and VS Code](https://www.gitpod.io/blog/root-docker-and-vscode/) and are already working on big plans we have for next year 🤓 
+We are excited about the things we announced yesterday around [Root, Docker and VS Code](https://www.gitpod.io/blog/root-docker-and-vscode/) and are already working on big plans we have for next year 🤓
 
 Ephemeral dev environments are going to democratize software development. Allowing anyone to get into a productive coding state on any of their projects and branches with the click of a button is a massive productivity boost. In addition we keep the entire devops pipeline in a centralized, managed system, which provides more security and observability to today’s developer teams.
 
 We will continue to focus on automating the provisioning of dev environments that blend in with your existing workflow, integrate into your existing infrastructure and run on any cloud or your own clusters. [We do all of this in the open](https://github.com/gitpod-io/gitpod) and invite everyone to join us in building an open platform for secure, collaborative and always-ready-to-code development environments for all developers.
 
-If you want to learn more you can start with our [Introduction to Gitpod](http://www.gitpod.io/docs/). 
+If you want to learn more you can start with our [Introduction to Gitpod](http://www.gitpod.io/docs/).
 

src/pages/privacy.tsx

@@ -528,10 +528,10 @@ https://spectrum.chat/privacy.html</li>
                     Transfer of Data to Third Parties
 			</h3>
                 <p>
-                    We will transfer your personal data to a third party only (i) within the scope of legal provisions, 
-                    i.e. if we are obliged to transfer the data due to a government or court order, or, (ii) if applicable, 
-                    legal provisions authorize the transfer, e.g. if the transfer is required to pursue our legitimate 
-                    interests or to fulfil a contract, for example in case of mergers and acquisitions, (iii) or if you 
+                    We will transfer your personal data to a third party only (i) within the scope of legal provisions,
+                    i.e. if we are obliged to transfer the data due to a government or court order, or, (ii) if applicable,
+                    legal provisions authorize the transfer, e.g. if the transfer is required to pursue our legitimate
+                    interests or to fulfil a contract, for example in case of mergers and acquisitions, (iii) or if you
                     give your explicit consent.
 			</p>
 

src/pages/terms.tsx

@@ -503,31 +503,31 @@ const TermsPage: React.SFC<{}> = () => (
                 </p>
             <ol>
                 <li>
-                    <strong>Gitpod, Inc.</strong>, a corporation incorporated and validly existing under the laws of the State of Delaware, 
-                    United States, registered with the Division of Corporations of the State of Delaware under file number 3353320 and with 
+                    <strong>Gitpod, Inc.</strong>, a corporation incorporated and validly existing under the laws of the State of Delaware,
+                    United States, registered with the Division of Corporations of the State of Delaware under file number 3353320 and with
                     business address at: 1390 Market Street, Suite 200, San Francisco. CA 94102, United States ("<strong>Gitpod, Inc.</strong>"); or
                     </li>
                 <li>
                     another third-party designated in our discretion ("<strong>Third-Party</strong>")
                     </li>
             </ol>
             <p>
-                by way of a transfer of contract with discharging effect (Vertragsübernahme mit schuldbefreiender Wirkung) with the effect that 
-                Gitpod, Inc. or the Third-Party becomes your new contractual partner in our stead and assumes all our rights and obligations under 
+                by way of a transfer of contract with discharging effect (Vertragsübernahme mit schuldbefreiender Wirkung) with the effect that
+                Gitpod, Inc. or the Third-Party becomes your new contractual partner in our stead and assumes all our rights and obligations under
                 this Agreement.
                 </p>
             <p>
-                We will notify you of a contemplated transfer of this Agreement and provide you with the identity of your new contractual partner 
-                in text form with at least four three weeks' notice prior to the contemplated transfer of this Agreement becoming effective 
-                ("<strong>Transfer Notice</strong>"). 
+                We will notify you of a contemplated transfer of this Agreement and provide you with the identity of your new contractual partner
+                in text form with at least four three weeks' notice prior to the contemplated transfer of this Agreement becoming effective
+                ("<strong>Transfer Notice</strong>").
                 </p>
             <p>
-                In case of a contemplated transfer of this Agreement to a Third-Party you shall be entitled to terminate this Agreement without 
-                notice and without any additional cause being required. This termination right must be exercised within six weeks following receipt 
+                In case of a contemplated transfer of this Agreement to a Third-Party you shall be entitled to terminate this Agreement without
+                notice and without any additional cause being required. This termination right must be exercised within six weeks following receipt
                 of the Transfer Notice and must be exercised in text form.
                 </p>
             <p>
-                The above termination right shall not exist in case of a transfer of this Agreement to Gitpod, Inc. Other rights you may have to 
+                The above termination right shall not exist in case of a transfer of this Agreement to Gitpod, Inc. Other rights you may have to
                 terminate the Agreement with or without cause shall remain unaffected.
                 </p>