Skip to content

Commit 18cd254

Browse files
committed
Update README.md
Formatting: changed the heading size
1 parent 03edc98 commit 18cd254

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

week0/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
## This is a test lesson and its aim is to let you practice with that flow we're going to follow.
1+
#### This is a test lesson and its aim is to let you practice with that flow we're going to follow.
22

3-
### Before you start
3+
##### Before you start
44

55
1. You should be familiar with Git. At least with Git basics. To do so please visit http://git-scm.com/documentation
66
2. Create an GitHub account if you still don't have one - https://github.com/join
77
3. Install Git on your local environment - http://git-scm.com/downloads
88
4. Learn how to fork repositories - https://help.github.com/articles/fork-a-repo
99
5. Learn how to work with pull-requests - https://help.github.com/articles/using-pull-requests
1010

11-
### To start the lesson please follow the instructions below:
11+
##### To start the lesson please follow the instructions below:
1212

1313
1. Fork this repository to your GitHub account
1414
2. Clone your fork to your local environment
@@ -19,4 +19,4 @@
1919
7. Initiate, review and send a pull-request
2020
8. Wait until the pull-request is reviewed. It could be either closed or merged, in other terms: rejected or accepted. In any case take into account all comments if those were done.
2121
9. If the pull-request was closed (rejected) carefully read our comments, fix issues and go back to the step 6.
22-
10. If the pull-request was merged (accepted), our congratulations, you've just finished the lesson. Move forward to the next one.
22+
10. If the pull-request was merged (accepted), our congratulations, you've just finished the lesson. Move forward to the next one.

0 commit comments

Comments
 (0)