From 8c00601687c56530d3802bd7a457992797586abd Mon Sep 17 00:00:00 2001 From: Anton Paras Date: Mon, 20 Nov 2017 03:31:13 -0800 Subject: [PATCH] Fix typo: "as follow" to "as follows" (#102) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9f45c7e..b955051 100644 --- a/README.md +++ b/README.md @@ -80,7 +80,7 @@ There are a set of rules to keep in mind: ### 1.2 Git workflow -Because of most of the reasons above, we use [Feature-branch-workflow](https://www.atlassian.com/git/tutorials/comparing-workflows#feature-branch-workflow) with [Interactive Rebasing](https://www.atlassian.com/git/tutorials/merging-vs-rebasing#the-golden-rule-of-rebasing) and some elements of [Gitflow](https://www.atlassian.com/git/tutorials/comparing-workflows#gitflow-workflow) (naming and having a develop branch). The main steps are as follow: +Because of most of the reasons above, we use [Feature-branch-workflow](https://www.atlassian.com/git/tutorials/comparing-workflows#feature-branch-workflow) with [Interactive Rebasing](https://www.atlassian.com/git/tutorials/merging-vs-rebasing#the-golden-rule-of-rebasing) and some elements of [Gitflow](https://www.atlassian.com/git/tutorials/comparing-workflows#gitflow-workflow) (naming and having a develop branch). The main steps are as follows: * For a new project, initialize a git repository in the project directory. __For subsequent features/changes this step should be ignored__. ```sh