Third pass at README update

Author: l4cr0ss

README.md

@@ -65,22 +65,22 @@ required for the bot to function. Finally, you must ensure that you have
 subscribed the bot users to the list of events it will need to receive in order
 to operate.
 
-1) First, navigate to `api.slack.com/apps` and create a new slack app. Give it
+1. First, navigate to `api.slack.com/apps` and create a new slack app. Give it
 a name and select the workspace that it will serve, and then click create.
 
-2) Enable socket mode by clicking on the menu of the same name and then
+2. Enable socket mode by clicking on the menu of the same name and then
 clicking on the toggle labelled "Enable Socket Mode". You'll be prompted to
 create an App Level Token which you must do next.
 
-2) App Level Token
+3. App Level Token
 
 This token is used by the bot to access the websocket event feed in version 3
 of the Slack API. The toggle you enabled in the previous step, "Enable Socket
 Mode", is what turns on the event feed. Assuming you've not already created an
 App Level Token you'll now be prompted to do so. Place it into the config file
 under the entry `app_key`.
 
-3) Bot User Token
+4. Bot User Token
 
 This token is used by the bot to interact with the workspace and users via
 Slack's conversations API. In order to create this token you must first
@@ -101,7 +101,6 @@ chat:write
 chat:write.customize
 chat:write.public
 dnd:read
-emoji:read
 groups:history
 groups:read
 groups:write
@@ -113,8 +112,6 @@ links:write
 mpim:history
 mpim:read
 mpim:write
-pins:read
-pins:write
 reactions:read
 reactions:write
 reminders:list
@@ -131,7 +128,7 @@ Access Token" (begins with `xoxb`) into the config file under the entry
 display name using the menu on the left labelled "Basic Information", if you
 want.
 
-4) Event subscription
+5. Event subscription
 
 NOTE: Make sure you toggle "Enable Socket" (step 2) before attempting this!
 
@@ -146,48 +143,47 @@ fine to select all of the event subscriptions here if you want to be on the simp
 ```
 app_mention
 app_mentions:read
+channels:history
 emoji_changed
 emoji:read
+groups:history
+im:history
 link_shared
 links:read
 message.channels
-channels:history
-message.groups
-groups:history
 message.im
-im:history
+message.groups
 message.mpim
 mpim:history
 reaction_added
 reactions:read
 reaction_removed
-reactions:read
 ```
 
 
 ## Installation
 
-1. Copy `config/config.json.template` to `config/config.json`
-2. Fill the APP and API token names in the config.json file.
-3. Add your user id (slack id, not the username) to `admin_users` group in `config/config.json`
+1. Copy _config/config.json.template_ to _config/config.json_
+2. Fill the APP and API token names in the _config.json_ file.
+3. Add your user id (slack id, not the username) to `admin_users` group in _config/config.json_
 4. If you want to use the wolfram alpha api, register a valid app id on http://products.wolframalpha.com/api/ and set `wolfram_app_id` in `config/config.json`
-5. Copy `intro_msg.template` to `intro_msg` and set a proper introduction message, which can be shown with `!intro`
+5. Copy _intro_msg.template_ to _intro_msg_ and set a proper introduction message, which can be shown with `!intro`
 6. `docker build -t ota-challenge-bot .`
 7. `docker run -it --rm --name live-ota-challenge-bot ota-challenge-bot`
 
 
 ## Development
 
-1. Copy `config/config.json.template` to `config/config.json`
-2. Fill the API token and bot name in the config.json file.
+1. Copy _config/config.json.template_ to _config/config.json_
+2. Fill the API token and bot name in the _config.json_ file.
 3. Create a virtual env: `python3 -m venv .venv`
 4. Enter the virtual env: `source .venv/bin/activate`
 5. Install requirements: `pip install -r requirements.txt`
 
 
 ## Using git support for uploading solve updates
 
-1. Copy `config/config_solvetracker.json.template` to `config/config_solvetracker.json`.
+1. Copy _config/config_solvetracker.json.template_ to _config/config_solvetracker.json_.
 2. Configure the git account, the local repo and the remote path, which should be used to access your git repository.
 
 Example:
@@ -202,20 +198,20 @@ Example:
 }
 ```
 
-Alternatively, you may decide to omit the "git_repopass" entry. In such an event (or if the entry is left blank) then the handler will attempt to push to the configured "git_remoteuri" using the `git` protocol, including using any SSH identities you may have configured.
+Alternatively, you may decide to omit the `git_repopass` entry. In such an event (or if the entry is left blank) then the handler will attempt to push to the configured "git_remoteuri" using the `git` protocol, including using any SSH identities you may have configured.
 Note: If you configure the solvetracker this way, you need to make sure you are using an SSH identity without a passphrase.
 
 3. Update the templates in `templates` according to your preferences (or go with the default ones).
-4. Make sure that there's a `_posts` and `_stats` folder in your git repository.
+4. Make sure that there's a __posts_ and __stats_ folder in your git repository.
 5. You should be good to go now and git support should be active on the next startup. You can now use the `postsolves` command to push blog posts with the current solve status to git.
 
 
 ## Using Link saver
 
 1. Setup a github repo with jekyll and staticman (e.g. https://github.com/ujjwal96/links).
-2. Copy `config/config_savelink.json.template` to `config/config_savelink.json`.
+2. Copy _config/config_savelink.json.template_ to _config/config_savelink.json_.
 3. Configure the git repo and branch to be used.
-4. Add the decrypted staticman-token used in `staticman.yml` in the config.
+4. Add the decrypted staticman-token used in _staticman.yml_ in the config.
 5. Add a link to your repo, so people can look it up via `showlinkurl`
 
 Example:
@@ -231,7 +227,7 @@ Example:
 
 ## Archive reminder
 
-To enable archive reminders set an offset (in hours) in `config/config.json` for `archive_ctf_reminder_offset`. Clear or remove the setting to disable reminder handling.
+To enable archive reminders set an offset (in hours) in _config/config.json_ for `archive_ctf_reminder_offset`. Clear or remove the setting to disable reminder handling.
 
 If active, the bot will create a reminder for every bot admin on `!endctf` to inform him, when the ctf was finished for the specified time and it should be archived.
 
@@ -245,7 +241,7 @@ Example (for being reminded one week after the ctf has finished):
 
 ## Log command deletion
 
-To enable logging of deleting messages containing specific keywords, set `delete_watch_keywords` in `config/config.json` to a comma separated list of keywords. 
+To enable logging of deleting messages containing specific keywords, set `delete_watch_keywords` in _config/config.json_ to a comma separated list of keywords. 
 Clear or remove the setting to disable deletion logging.
 
 Example