Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit 38180ef

Browse files
atwixfirsteratwixfirster
committed
#5245: Markdown linting: Hard tabs (MD010) #5245 
1 parent df06ae8 commit 38180ef

File tree

469 files changed

+7817
-7835
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

469 files changed

+7817
-7835
lines changed

‎_includes/browsers/supported-browsers.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
Storefront and Admin:
22

3-
* Internet Explorer 11 or later, Microsoft Edge, latest–1
4-
* Firefox latest, latest–1 (any operating system)
5-
* Chrome latest, latest–1 (any operating system)
6-
* Safari latest, latest–1 (Mac OS only)
7-
* Safari Mobile for iPad 2, iPad Mini, iPad with Retina Display (iOS 7 or later), for desktop storefront
8-
* Safari Mobile for iPhone 4 or later; iOS 7 or later, for mobile storefront
9-
* Chrome for mobile latest–1 (Android 4 or later) for mobile storefront
3+
* Internet Explorer 11 or later, Microsoft Edge, latest–1
4+
* Firefox latest, latest–1 (any operating system)
5+
* Chrome latest, latest–1 (any operating system)
6+
* Safari latest, latest–1 (Mac OS only)
7+
* Safari Mobile for iPad 2, iPad Mini, iPad with Retina Display (iOS 7 or later), for desktop storefront
8+
* Safari Mobile for iPhone 4 or later; iOS 7 or later, for mobile storefront
9+
* Chrome for mobile latest–1 (Android 4 or later) for mobile storefront
1010

1111
Here, _latest–1_ means one major version earlier than the latest released version.

‎_includes/cloud/cli-get-started.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,35 @@
11

2-
1. Log in to your local development system, or switch to, the [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html).
3-
2. Change to a directory to which the Magento file system owner has write access.
4-
2. Enter the following command in a terminal to log in to your project:
2+
1. Log in to your local development system, or switch to, the [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html).
3+
2. Change to a directory to which the Magento file system owner has write access.
4+
2. Enter the following command in a terminal to log in to your project:
55

6-
magento-cloud login
7-
3. List your projects. With the project ID, you can complete additional commands.
6+
magento-cloud login
7+
3. List your projects. With the project ID, you can complete additional commands.
88

9-
magento-cloud project:list
10-
4. If necessary, clone the project to your local. You should have cloned when setting up your local development workspace.
9+
magento-cloud project:list
10+
4. If necessary, clone the project to your local. You should have cloned when setting up your local development workspace.
1111

12-
magento-cloud project:get <project ID>
12+
magento-cloud project:get <project ID>
1313

14-
4. Change to a project directory. For example, `cd /var/www/html/magento2`
15-
4. List environments in the project. Every environment includes an active Git branch of your code, database, environment variables, configurations, and services.
14+
4. Change to a project directory. For example, `cd /var/www/html/magento2`
15+
4. List environments in the project. Every environment includes an active Git branch of your code, database, environment variables, configurations, and services.
1616

17-
magento-cloud environment:list
17+
magento-cloud environment:list
1818

1919
{: .bs-callout .bs-callout-info}
20-
`magento-cloud environment:list`—displays environment hierarchies whereas the `git branch` command does not.
20+
`magento-cloud environment:list`—displays environment hierarchies whereas the `git branch` command does not.
2121

22-
5. Fetch origin branches to get the latest code:
22+
5. Fetch origin branches to get the latest code:
2323

24-
git fetch origin
25-
6. Check out, or switch to, a specific branch and environment. Git commands only checkout the Git branch. The Magento Cloud command also switches to the active environment.
24+
git fetch origin
25+
6. Check out, or switch to, a specific branch and environment. Git commands only checkout the Git branch. The Magento Cloud command also switches to the active environment.
2626

27-
magento-cloud environment:checkout <environment ID>
27+
magento-cloud environment:checkout <environment ID>
2828

29-
To create a new environment, use `magento-cloud environment:branch <environment name> <parent environment ID>`
30-
8. Pull any updated code to your local for the environment ID (which is the Git branch):
29+
To create a new environment, use `magento-cloud environment:branch <environment name> <parent environment ID>`
30+
8. Pull any updated code to your local for the environment ID (which is the Git branch):
3131

32-
git pull origin <environment ID>
32+
git pull origin <environment ID>
3333
7. Create a [snapshot]({{ page.baseurl }}/cloud/project/project-webint-snap.html) of the environment as a backup:
3434

3535
magento-cloud snapshot:create -e <environment ID>

‎_includes/cloud/cloud-fastly-manage-vcl-from-admin.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,11 +23,11 @@ You can delete custom VCL snippet code from your Fastly configuration by uploadi
2323

2424
- Upload an empty version of the snippet file to Fastly to remove the VCL logic from the active VCL version:
2525

26-
- Edit the snippet and delete the **VCL** snippet content.
26+
- Edit the snippet and delete the **VCL** snippet content.
2727

28-
- Save the configuration.
28+
- Save the configuration.
2929

30-
- Upload the VCL to Fastly to apply your changes.
30+
- Upload the VCL to Fastly to apply your changes.
3131

3232
- Use the Fastly API [Delete custom VCL snippet]({{ page.baseurl }}/cloud/cdn/cloud-vcl-custom-snippets.html#manage-vcl) operation
3333
to delete the snippet completely, or submit a Magento support ticket to request deletion.

‎_includes/cloud/composer-name.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -2,23 +2,23 @@ This section discusses how to get a module's Composer name and its version from
22

33
#### To get the module's Composer name from Magento Marketplace:
44

5-
1. Log in to [Magento Marketplace](https://marketplace.magento.com) with the username and password you used to purchase the component.
6-
2. In the upper right corner, click **&lt;your username>** > **My Account** as the following figure shows.
5+
1. Log in to [Magento Marketplace](https://marketplace.magento.com) with the username and password you used to purchase the component.
6+
2. In the upper right corner, click **&lt;your username>** > **My Account** as the following figure shows.
77

8-
![Access your Marketplace account]({{ site.baseurl }}/common/images/cloud_marketplace-account.png){:width="650px"}
9-
3. On the My Account page, click **My Purchases** as the following figure shows.
8+
![Access your Marketplace account]({{ site.baseurl }}/common/images/cloud_marketplace-account.png){:width="650px"}
9+
3. On the My Account page, click **My Purchases** as the following figure shows.
1010

11-
![Marketplace purchase history]({{ site.baseurl }}/common/images/cloud_marketplace-purch-history.png){:width="650px"}
12-
4. On the My Purchases page, click **Technical Details** for the module you purchased as the following figure shows.
11+
![Marketplace purchase history]({{ site.baseurl }}/common/images/cloud_marketplace-purch-history.png){:width="650px"}
12+
4. On the My Purchases page, click **Technical Details** for the module you purchased as the following figure shows.
1313

14-
![Technical details shows the module's Composer name]({{ site.baseurl }}/common/images/cloud_marketplace-download-invoice.png){:width="200px"}
15-
5. Click **Copy** to copy the component name to the clipboard.
16-
5. Open a text editor.
17-
6. Paste the module name in the text editor.
18-
6. Append a colon character (`:`) to the component name.
19-
7. In **Technical Details** on the My Purchases page, click **Copy** to copy the version to the clipboard.
20-
8. Append the version number to the component name after the colon.
14+
![Technical details shows the module's Composer name]({{ site.baseurl }}/common/images/cloud_marketplace-download-invoice.png){:width="200px"}
15+
5. Click **Copy** to copy the component name to the clipboard.
16+
5. Open a text editor.
17+
6. Paste the module name in the text editor.
18+
6. Append a colon character (`:`) to the component name.
19+
7. In **Technical Details** on the My Purchases page, click **Copy** to copy the version to the clipboard.
20+
8. Append the version number to the component name after the colon.
2121

22-
A sample follows:
22+
A sample follows:
2323

24-
pixlee/magento2:1.0.1
24+
pixlee/magento2:1.0.1

‎_includes/cloud/enable-ssh.md

Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ The SSH keys require the following:
77

88
For more information on SSH keys, see the following:
99

10-
* [Connecting to GitHub with SSH](https://help.github.com/articles/connecting-to-github-with-ssh/)
11-
* [Manually generating your SSH key in Windows](https://docs.joyent.com/public-cloud/getting-started/ssh-keys/generating-an-ssh-key-manually/manually-generating-your-ssh-key-in-windows)
12-
* [ssh-keygen man page](http://linux.die.net/man/1/ssh-keygen)
10+
* [Connecting to GitHub with SSH](https://help.github.com/articles/connecting-to-github-with-ssh/)
11+
* [Manually generating your SSH key in Windows](https://docs.joyent.com/public-cloud/getting-started/ssh-keys/generating-an-ssh-key-manually/manually-generating-your-ssh-key-in-windows)
12+
* [ssh-keygen man page](http://linux.die.net/man/1/ssh-keygen)
1313

1414
## Locate an existing SSH key pair {#existing}
1515

@@ -19,11 +19,11 @@ You can quickly verify if you have SSH keys by entering commands using terminal
1919

2020
To check for SSH keys, enter the following command:
2121

22-
ls ~/.ssh
22+
ls ~/.ssh
2323

2424
If you have SSH keys, a directory listing is displayed similar to the following:
2525

26-
id_rsa id_rsa.pub known_hosts
26+
id_rsa id_rsa.pub known_hosts
2727

2828
If you do not have SSH keys, you need to generate the keys for adding to your Magento ECE account and GitHub account. See [Create a new SSH key pair](#ssh-create-new-key-pair).
2929

@@ -94,7 +94,7 @@ After adding the SSH keys, test the SSH connection to GitHub:
9494

9595
1. In the terminal, enter the following command:
9696

97-
ssh -T git@github.com
97+
ssh -T git@github.com
9898

9999
2. You may see a warning that the authenticity of the host can't be established followed by an RSA fingerprint. Enter `yes` to continue.
100100
@@ -104,23 +104,23 @@ After adding the SSH keys, test the SSH connection to GitHub:
104104
105105
You can add SSH keys to your account in any of the following ways:
106106
107-
* Using the [{{site.data.var.ece}} CLI](#add-key-cli)
108-
* Using the [{{site.data.var.ece}} Web Interface](#add-key-web)
107+
* Using the [{{site.data.var.ece}} CLI](#add-key-cli)
108+
* Using the [{{site.data.var.ece}} Web Interface](#add-key-web)
109109
110110
### Add a key using the CLI {#add-key-cli}
111111
112112
To add an SSH key using the CLI:
113113
114-
1. Open a terminal application on your local.
115-
2. If you haven't done so already, log in (or switch to) the [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html) to the server on which your SSH keys are located.
114+
1. Open a terminal application on your local.
115+
2. If you haven't done so already, log in (or switch to) the [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html) to the server on which your SSH keys are located.
116116

117-
3. Log in to your project:
117+
3. Log in to your project:
118118

119-
magento-cloud login
119+
magento-cloud login
120120

121-
3. Add the key:
121+
3. Add the key:
122122

123-
magento-cloud ssh-key:add ~/.ssh/id_rsa.pub
123+
magento-cloud ssh-key:add ~/.ssh/id_rsa.pub
124124

125125
#### Add a key using the Project Web Interface {#add-key-web}
126126

@@ -131,25 +131,25 @@ You will select and add your SSH public key to each environment in your account.
131131

132132
To add an SSH key using the Project Web Interface:
133133

134-
1. Copy your SSH public key to the clipboard.
134+
1. Copy your SSH public key to the clipboard.
135135

136-
If you do not already have SSH keys on that machine, see [GitHub documentation](https://help.github.com/articles/generating-an-ssh-key) to create them.
137-
2. Login and access your project through the [Project Web Interface](https://accounts.magento.cloud).
138-
3. In your selected branch, an icon displays if you do not have an SSH key added.
136+
If you do not already have SSH keys on that machine, see [GitHub documentation](https://help.github.com/articles/generating-an-ssh-key) to create them.
137+
2. Login and access your project through the [Project Web Interface](https://accounts.magento.cloud).
138+
3. In your selected branch, an icon displays if you do not have an SSH key added.
139139

140-
![No SSH key]({{ site.baseurl }}/common/images/cloud_ssh-key-install.png)
141-
4. Copy and paste the content of your public SSH key in the screen.
140+
![No SSH key]({{ site.baseurl }}/common/images/cloud_ssh-key-install.png)
141+
4. Copy and paste the content of your public SSH key in the screen.
142142

143-
![Add SSH key]({{ site.baseurl }}/common/images/cloud_ssh-key-add.png)
144-
5. Follow the prompts on your screen to complete the task.
143+
![Add SSH key]({{ site.baseurl }}/common/images/cloud_ssh-key-add.png)
144+
5. Follow the prompts on your screen to complete the task.
145145

146146
## Set global Git variables
147147

148148
Set required global Git variables on the machine to commit or push to a Git branch. These variables set Git credentials for accessing your GitHub account.
149149

150150
To set variables, enter the following commands on every workspace:
151151

152-
git config --global user.name "<your name>"
153-
git config --global user.email <your e-mail address>
152+
git config --global user.name "<your name>"
153+
git config --global user.email <your e-mail address>
154154

155155
For more information, see [First-Time Git Setup](https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup#_first_time)

‎_includes/cloud/new-project-from-template.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
11
1. Access your account. You can open the email you received from Magento Cloud (accounts@magento.cloud) and click the _Access your project now_ link. Or you can log in to [your {{site.data.var.ee}} account](https://accounts.magento.cloud).
22
2. Click the _This project has no code yet_ link next to the Project name.
33

4-
![Project without code]({{ site.baseurl }}/common/images/cloud_project_empty.png)
4+
![Project without code]({{ site.baseurl }}/common/images/cloud_project_empty.png)
55

66
3. Enter a name for the project.
77

8-
![Project name]({{ site.baseurl }}/common/images/cloud_project_name.png)
8+
![Project name]({{ site.baseurl }}/common/images/cloud_project_name.png)
99

1010
4. Click **Create a blank site from a template** and click **Continue**. We recommend starting with the Magento template as your initial project option. If you have an existing Magento deployment, you can later import code, extensions, themes, and data after fully deploying this base Magento code.
1111

12-
![Create a site using the sample Magento project]({{ site.baseurl }}/common/images/cloud_project_template.png){:width="650px"}
12+
![Create a site using the sample Magento project]({{ site.baseurl }}/common/images/cloud_project_template.png){:width="650px"}
1313

1414
5. When prompted, enter your {{site.data.var.ee}} [Magento authentication keys]({{ page.baseurl }}/install-gde/prereq/connect-auth.html) in the provided fields. You created these keys earlier in the Magento Marketplace. Enter the private and public keys and click **Finish**.
1515

16-
![Enter your authentication keys]({{ site.baseurl }}/common/images/cloud-project-magento-auth-creds.png){:width="650px"}
16+
![Enter your authentication keys]({{ site.baseurl }}/common/images/cloud-project-magento-auth-creds.png){:width="650px"}
1717

18-
The keys are added to the `auth.json` file in the repository `master` branch, required for all created branches and deployments.
18+
The keys are added to the `auth.json` file in the repository `master` branch, required for all created branches and deployments.
1919

2020
6. Wait a few minutes while the project deploys. A status of _Pending_ displays until completed, similar to the following:
2121

22-
![Your sample Magento project]({{ site.baseurl }}/common/images/cloud_project_template2.png){:width="650px"}
22+
![Your sample Magento project]({{ site.baseurl }}/common/images/cloud_project_template2.png){:width="650px"}
2323

2424
7. After the project deploys, **Success** displays next to the name of your project.

0 commit comments

Comments
 (0)