#5245: Hard tabs. Folder: guides/cloud

Author: atwixfirster

guides/v2.2/cloud/basic-information/starter-architecture.md

@@ -74,19 +74,19 @@ The Production and Staging environments include the following technologies. You
 
 Each service runs in its own secure container. Containers are managed together in the project. Some services are built-in, such as the following:
 
-*	HTTP router (handling incoming requests, but also caching and redirects)
-*	PHP application server
-*	Git
-*	Secure Shell (SSH)
+* HTTP router (handling incoming requests, but also caching and redirects)
+* PHP application server
+* Git
+* Secure Shell (SSH)
 
 You can even have multiple applications running in the same project. Building a microservice oriented architecture with {{site.data.var.ee}} is as easy as managing a monolithic application.
 
 ### Software versions {#cloud-arch-software}
 
 {{site.data.var.ece}} uses:
 
-*	Operating system: Debian GNU/Linux 8 (jessie)
-*	Web server: [nginx](https://glossary.magento.com/nginx) 1.8
+* Operating system: Debian GNU/Linux 8 (jessie)
+* Web server: [nginx](https://glossary.magento.com/nginx) 1.8
 
 You cannot upgrade the operating system and web server software to a new version, but you can configure versions for the following software:
 
@@ -100,9 +100,9 @@ In the Staging and Production environments, you use Fastly for CDN and caching.
 
 You use the following files to configure the software versions that you want to use in your implementation.
 
-*	[`.magento.app.yaml`]({{ page.baseurl }}/cloud/project/project-conf-files_magento-app.html)
-*	[`routes.yaml`]({{ page.baseurl }}/cloud/project/project-conf-files_routes.html)
-*	[`services.yaml`]({{ page.baseurl }}/cloud/project/project-conf-files_services.html)
+* [`.magento.app.yaml`]({{ page.baseurl }}/cloud/project/project-conf-files_magento-app.html)
+* [`routes.yaml`]({{ page.baseurl }}/cloud/project/project-conf-files_routes.html)
+* [`services.yaml`]({{ page.baseurl }}/cloud/project/project-conf-files_services.html)
 
 ### Backup and disaster recovery {#backup}
 

guides/v2.2/cloud/before/before-setup-env-2_clone.md

@@ -23,52 +23,52 @@ Some Git commands cannot complete an action in your {{site.data.var.ece}} projec
 
 #### To clone a project master environment:
 
-1.  Log in to your local workstation with a [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html) account.
+1. Log in to your local workstation with a [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html) account.
 
-1.  Change to the web server or virtual host _docroot_ directory.
+1. Change to the web server or virtual host _docroot_ directory.
 
-1.  Log in to the Magento Cloud CLI.
+1. Log in to the Magento Cloud CLI.
 
-    ```bash
-    magento-cloud login
-    ```
+   ```bash
+   magento-cloud login
+   ```
 
-1.  List your projects.
+1. List your projects.
 
-    ```bash
-    magento-cloud project:list
-    ```
+   ```bash
+   magento-cloud project:list
+   ```
 
-1.  Clone a project.
+1. Clone a project.
 
-    ```bash
-    magento-cloud project:get <project-ID>
-    ```
+   ```bash
+   magento-cloud project:get <project-ID>
+   ```
 
-    When prompted for a directory name, enter `magento2`.
+   When prompted for a directory name, enter `magento2`.
 
-1.  Change to the `magento2` directory.
+1. Change to the `magento2` directory.
 
-1.  List available environments for the project.
+1. List available environments for the project.
 
-    ```bash
-    magento-cloud environment:list
-    ```
+   ```bash
+   magento-cloud environment:list
+   ```
 
-    {:.bs-callout .bs-callout-info}
-    The `magento-cloud environment:list` command displays environment hierarchies, whereas the `git branch` command does not.
+   {:.bs-callout .bs-callout-info}
+   The `magento-cloud environment:list` command displays environment hierarchies, whereas the `git branch` command does not.
 
-1.  Fetch the remote branches.
+1. Fetch the remote branches.
 
-    ```bash
-    git fetch magento
-    ```
+   ```bash
+   git fetch magento
+   ```
 
-1.  Pull updated code.
+1. Pull updated code.
 
-    ```bash
-    git pull magento <environment-ID>
-    ```
+   ```bash
+   git pull magento <environment-ID>
+   ```
 
 ## Change the Magento ADMIN variables
 
@@ -79,7 +79,7 @@ We recommend changing the environment-level variables for the Magento Admin URL
 -  **ADMIN_PASSWORD**—A password for the administrative user. When the project was created, the License Owner received a default password in email.
 -  **ADMIN_URL**— The relative URL to access the Admin panel, such as `<domain>/admin`. For security reasons, we recommend you choose a value other than `admin` or `backend` or another term that is easy to guess.
 
-{:.bs-callout .bs-callout-info}
+{: .bs-callout-info }
 Make note of any updated values so that you can use them to install Magento from the command line and to verify the installation. The values for the `ADMIN_EMAIL`, `ADMIN_USERNAME`, and `ADMIN_PASSWORD` variables are used only for installation.
 
 #### To view existing variables: {#variablelist}
@@ -128,56 +128,56 @@ Every time you add or modify a variable using the web interface or the CLI, the
 
 Alternatively, you can add or update variables in the Project Web Interface.
 
-1.  Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud).
+1. Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud).
 
-1.  Click the **Configure environment** gear icon ![Configure your environment]({{ site.baseurl }}/common/images/cloud_edit-project.png) next to the Project name.
+1. Click the **Configure environment** gear icon ![Configure your environment]({{ site.baseurl }}/common/images/cloud_edit-project.png) next to the Project name.
 
-	![Project without code]({{ site.baseurl }}/common/images/cloud_project_empty.png)
+   ![Project without code]({{ site.baseurl }}/common/images/cloud_project_empty.png)
 
-1.  Select the **Variables** tab.
+1. Select the **Variables** tab.
 
-1.  Click **Add Variable**.
+1. Click **Add Variable**.
 
-1.  Enter the **Name** and **Value** for the variable. For example, enter `ADMIN_EMAIL` and your License Owner email address or another accessible email for resetting the password for the default admin account.
+1. Enter the **Name** and **Value** for the variable. For example, enter `ADMIN_EMAIL` and your License Owner email address or another accessible email for resetting the password for the default admin account.
 
-	![Project variable]({{ site.baseurl }}/common/images/cloud_project_variable.png)
+   ![Project variable]({{ site.baseurl }}/common/images/cloud_project_variable.png)
 
-1.  Click **Add variable**. After you add the variable, wait until deployment completes.
+1. Click **Add variable**. After you add the variable, wait until deployment completes.
 
 ## Create a branch for development {#branch}
 
 After cloning your project and updating the Magento administrator account configuration, you can branch for development. As stated earlier, you must create an environment using the `magento-cloud environment:branch <branch-name>` command or the Project Web Interface for the environment to become _active_.
 
 - For [Starter]({{ page.baseurl }}/cloud/basic-information/starter-develop-deploy-workflow.html#clone-branch), consider creating a branch for `staging`, then create a development branch based on the `staging` branch.
-* For [Pro]({{ page.baseurl }}/cloud/architecture/pro-develop-deploy-workflow.html), create development branches based on the Integration environment.
+- For [Pro]({{ page.baseurl }}/cloud/architecture/pro-develop-deploy-workflow.html), create development branches based on the Integration environment.
 
 #### To branch from master:
 
-1.  Do one of the following from the CLI.
+1. Do one of the following from the CLI.
 
-    -  To create a new environment:
+   - To create a new environment:
 
-        ```bash
-        magento-cloud branch <environment-name> <parent-environment-ID>
-        ```
+      ```bash
+      magento-cloud branch <environment-name> <parent-environment-ID>
+      ```
 
-    -   To check out an existing environment:
+   - To check out an existing environment:
 
-        ```bash
-        magento-cloud checkout <environment-name>
-        ```
+      ```bash
+      magento-cloud checkout <environment-name>
+      ```
 
-1.  Update dependencies.
+1. Update dependencies.
 
-    ```bash
-    composer --no-ansi --no-interaction install --no-progress --prefer-dist --optimize-autoloader
-    ```
+   ```bash
+   composer --no-ansi --no-interaction install --no-progress --prefer-dist --optimize-autoloader
+   ```
 
-1.  Create a [snapshot]({{ page.baseurl }}/cloud/project/project-webint-snap.html) of the environment.
+1. Create a [snapshot]({{ page.baseurl }}/cloud/project/project-webint-snap.html) of the environment.
 
-    ```bash
-    magento-cloud snapshot:create -e <environment-ID>
-    ```
+   ```bash
+   magento-cloud snapshot:create -e <environment-ID>
+   ```
 
 #### Next step:
 [Install Magento]({{ page.baseurl }}/cloud/before/before-setup-env-install.html)

guides/v2.2/cloud/before/before-workspace-file-sys-owner.md

@@ -24,68 +24,85 @@ Create the Magento file system owner with a strong password. Magento file system
 
 To create the Magento file system owner, enter the following command as a user with `root` privileges:
 
-	adduser <username>
+```bash
+adduser <username>
+```
 
 To give the user a password, enter the following command as a user with `root` privileges:
 
-	passwd <username>
+```bash
+passwd <username>
+```
 
 Follow the prompts on your screen to create a password for the user.
 
-{: .bs-callout .bs-callout-warning}
+{: .bs-callout-warning }
 If you do not have `root` privileges on your Magento server, you can use another local user account. Confirm that the user has a strong password and continue with [Put the Magento file system owner in the web server group](#install-update-depend-user-add2group).
 
 For example, to create a user named `magento_user` and give the user a password, enter:
 
-	sudo adduser magento_user
-	sudo passwd magento_user
+```bash
+sudo adduser magento_user
+```
 
-{: .bs-callout .bs-callout-warning}
+```bash
+sudo passwd magento_user
+```
+
+{: .bs-callout-warning }
 Because the point of creating this user is to provide added security, it is essential that you create a strong password.
 
 ## Find the web server user's group {#install-update-depend-user-findgroup}
 
 To find the web server user's group:
 
-*	CentOS:
+* CentOS:
+
+   ```bash
+   grep -E -i '^user|^group' /etc/httpd/conf/httpd.conf
+   ```
+
+   or
 
-    ```bash
-    grep -E -i '^user|^group' /etc/httpd/conf/httpd.conf
-    ```
-    or
-    ```bash
-    grep -Ei '^user|^group' /etc/httpd/conf/httpd.conf
-    ```
+   ```bash
+   grep -Ei '^user|^group' /etc/httpd/conf/httpd.conf
+   ```
 
-Typically, the user and group name are both `apache`
+   Typically, the user and group name are both `apache`
 
-*	Ubuntu: `ps aux | grep apache` to find the apache user, then `groups <apache user>` to find the group
+* Ubuntu: `ps aux | grep apache` to find the apache user, then `groups <apache user>` to find the group
 
-	Typically, the username and the group name are both `www-data`
+   Typically, the username and the group name are both `www-data`
 
 ## Put the Magento file system owner in the web server's primary group {#install-update-depend-user-add2group}
 
 Assuming the typical Apache group name for CentOS and Ubuntu, enter the following command as a user with `root` privileges:
 
-*	CentOS: `usermod -g apache <username>`
-*	Ubuntu: `usermod -g www-data <username>`
+* CentOS: `usermod -g apache <username>`
+* Ubuntu: `usermod -g www-data <username>`
 
 For example, to add the user `magento_user` to the `apache` primary group on CentOS:
 
-	usermod -g apache magento_user
+```bash
+usermod -g apache magento_user
+```
 
 To confirm your Magento user is a member of the web server group, enter the following command:
 
-	groups <username>
+```bash
+groups <username>
+```
 
 A sample result follows:
 
-	magento_user : apache
+```terminal
+magento_user : apache
+```
 
 To complete the task, restart the web server:
 
-*	Ubuntu: `service apache2 restart`
-*	CentOS: `service httpd restart`
+* Ubuntu: `service apache2 restart`
+* CentOS: `service httpd restart`
 
 #### Next step:
 [Clone and branch the project]({{ page.baseurl }}/cloud/before/before-setup-env-2_clone.html)