Change all README numbered lists to use the same number (1.)

README.md

@@ -40,12 +40,12 @@ Contains all resources and information UX Designers need.
 ### Activating them!
 1. Have a Mac with [Sketch](https://www.sketchapp.com/) installed in the /Applications folder
-2. Copy the `pre-commit` file into your `.git/hooks/` folder
+1. Copy the `pre-commit` file into your `.git/hooks/` folder
     - *The pre-commit hook will auto generate preview images out of your sketch pages*
     - *[Issue for Autogenerated Sketch Previews Discussion](https://gitlab.com/gitlab-org/gitlab-design/issues/15)*
-4. Install [Sketch Toolbox](http://sketchtoolbox.com/)
-5. Install [Sketch Measure Plugin](https://github.com/utom/sketch-measure) with the Sketch Toolbox
-3. Read on :)
+1. Install [Sketch Toolbox](http://sketchtoolbox.com/)
+1. Install [Sketch Measure Plugin](https://github.com/utom/sketch-measure) with the Sketch Toolbox
+1. Read on :)
 ## Repository Organization
@@ -77,28 +77,28 @@ As design files are mostly binary files, merge conflicts can easily get stuck in
 ### GitLab Designer Personal Folders
 1. In the `progress` directory, create your own folder
-2. In your own folder, create a subfolder for each issue/project you are working on
-3. Commit & Push changes
+1. In your own folder, create a subfolder for each issue/project you are working on
+1. Commit & Push changes
 ### Community Contribution :strawberry:
 Every designer can contribute to GitLab. For GitLab community members we have a [special folder](https://gitlab.com/gitlab-org/gitlab-design/tree/master/progress/community-contribution) in the `progress` directory where you can create and commit your own designs. So you have a consistent backup, which can also be used by other designers to iterate upon! Follow the following steps to contribute.
 1. Fork this repository and `git clone` it locally.
-2. Create a new branch based off from the master with `git checkout -b branchname`
-3. In the `community-contribution` directory, create your own folder based on your GitLab username following [the example](https://gitlab.com/gitlab-org/gitlab-design/tree/master/progress/community-contribution/@gitlabusername).
-4. In your own folder, create a subfolder for each issue/project you are working on.
-6. Review the files you are about to commit (with `git status -sb`), as __only files in your folder are allowed to be added or changed__!! If you have a hard time with this read through our [small section on Git](#oh-my-git)
-5. Commit and push your changes. Prefix your [good commit message](https://chris.beams.io/posts/git-commit/) with the project path and issue ID (e.g. `gitlab-ce#1337 Commit message`). This creates a commit note in the issue, making it easy for other people to contribute and fork the design (especially important if someone is out-of-office).
-6. Create a merge request and mention any [designer who manages this project](#project-managers).
+1. Create a new branch based off from the master with `git checkout -b branchname`
+1. In the `community-contribution` directory, create your own folder based on your GitLab username following [the example](https://gitlab.com/gitlab-org/gitlab-design/tree/master/progress/community-contribution/@gitlabusername).
+1. In your own folder, create a subfolder for each issue/project you are working on.
+1. Review the files you are about to commit (with `git status -sb`), as __only files in your folder are allowed to be added or changed__!! If you have a hard time with this read through our [small section on Git](#oh-my-git)
+1. Commit and push your changes. Prefix your [good commit message](https://chris.beams.io/posts/git-commit/) with the project path and issue ID (e.g. `gitlab-ce#1337 Commit message`). This creates a commit note in the issue, making it easy for other people to contribute and fork the design (especially important if someone is out-of-office).
+1. Create a merge request and mention any [designer who manages this project](#project-managers).
 ### Production Folders
 1. [Lock file](http://docs.gitlab.com/ee/user/project/file_lock.html)
-2. Pull changes
-3. Add our changes to the file
-4. Commit & Push changes
-5. [Unlock](http://docs.gitlab.com/ee/user/project/file_lock.html) file
+1. Pull changes
+1. Add our changes to the file
+1. Commit & Push changes
+1. [Unlock](http://docs.gitlab.com/ee/user/project/file_lock.html) file
 ## Naming Convention
 *TODO: We should write a pre-commit hook that checks for this naming convention, both in and outside sketch.*