readme: Re-format and fix grammar

The $ within the bash code snippets looks nice, but makes copying from the GitHub WebUI directly to the terminal unfeasible.

OTA probably belongs within the maintainer category, as it is a requirement for maintainership

OTA was gramatically corrected, by adding a "you" in the first sentence

Author: 306bobby-android

README.mkdn

@@ -17,42 +17,44 @@ sudo apt install bc bison build-essential ccache curl flex g++-multilib gcc-mult
 Install Repo tool
 ```bash
 # Make a directory where Repo will be stored and add it to the path
-$ mkdir ~/bin
-$ PATH=~/bin:$PATH
+ mkdir ~/bin
+ PATH=~/bin:$PATH
 
 # Download Repo itself
-$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
+ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
 
 # Make Repo executable
-$ chmod a+x ~/bin/repo
+ chmod a+x ~/bin/repo
 ```
 
 ### 1.2 Initializing Repo ###
 
 ```bash
 # Create a directory for the source files
 # This can be located anywhere (as long as the fs is case-sensitive)
-$ mkdir crDroid
-$ cd crDroid
+ mkdir crDroid
+ cd crDroid
 
 # Install Repo in the created directory
-$ repo init -u https://github.com/crdroidandroid/android.git -b 16.0 --git-lfs --no-clone-bundle
+ repo init -u https://github.com/crdroidandroid/android.git -b 16.0 --git-lfs --no-clone-bundle
 ```
 
+### 1.3 Syncing build environment ###
+
 This is what you will run each time you want to pull in upstream changes. Keep in mind that on your
 first run, it is expected to take a while as it will download all the required Android source files
 and their change histories.
 
 ```bash
 # Let Repo take care of all the hard work
-$ repo sync
+ repo sync
 ```
 
 ```bash
 # Run to prepare our devices list
-$ . build/envsetup.sh
+ . build/envsetup.sh
 # ... now run
-$ brunch devicecodename
+ brunch devicecodename
 ```
 
 ## 2. Contributions ##
@@ -63,6 +65,12 @@ To submit changes/patches, please send a pull request on GitHub. We will review
 
 Make sure you can follow our [rules-and-guidelines](https://github.com/crdroidandroid/rules-and-guidelines), then if all is right, just message Gabriel over [Telegram](https://telegram.me/gwolf2u) with the device you want to maintain.
 
+### 3.1 OTA ###
+So you posted on forums and your users are enjoying your build.  
+Well you can help out your users by letting them know when you fix stuff in your builds with the help of our OTA app.   
+Since crDroid Oreo, if you want to be on the official maintainers list, you'll need to provide OTA access.  
+You can set it up really easy by reading [android_vendor_crDroidOTA](https://github.com/crdroidandroid/android_vendor_crDroidOTA/blob/16.0/README.md) repo description.
+
 ## 4. crDroid features / overlays, translations, forum template and OTA ##
 
 ### 4.1 crDroid features / overlays ###
@@ -85,8 +93,3 @@ Build ready? Tested all features and translations are smooth?
 Why not share your build over your beloved forums?  
 To do so, we have made a [small template](https://github.com/crdroidandroid/crdroid_features/blob/16.0/ForumPostTemplate) to help out. Just edit what you need and let the downloads roll. :sunglasses:
 
-### 4.4 OTA ###
-So posted on forums and your users are enjoying your build.  
-Well you can help out your users by letting them know when you fix stuff in your builds with the help of our OTA app.   
-Since crDroid Oreo, if you want to be on the official maintainers list, you'll need to provide OTA access.  
-You can set it up really easy by reading [android_vendor_crDroidOTA](https://github.com/crdroidandroid/android_vendor_crDroidOTA/blob/16.0/README.md) repo description.