Simplify CONTRIBUTING.md

Author: jqtrde

CONTRIBUTING.md

@@ -3,8 +3,10 @@
 Hi there! Welcome to the tilesets-cli contributing document. Issues, comments, and pull requests are welcome. Please tag @mapbox/maps-api for any questions or reviews.
 
 ## Installation
+
 First, clone the repo and `cd` into the folder:
-```shell
+
+```bash
 # clone
 git clone [email protected]:mapbox/tilesets-cli.git
 cd tilesets-cli
@@ -21,36 +23,14 @@ tilesets --version
 ```
 
 ## Pre-commit hooks
+
 We use [pre-commit hooks](https://pre-commit.com/) to auto-format and validate code before committing. `pre-commit` is included with the `[test]` extras, but you must run:
-```
+
+```bash
 $ pre-commit install
 ```
 within the repo to have the actions specified in `.pre-commit-config.yaml` registered.
 
-After this, when committing, you'll see:
-```
-git commit -m 'update version'
-black....................................................................Passed
-Flake8...................................................................Passed
-```
-If your pre-commit hooks ran successfully. Note that `black` modifies your code, which means that if there is a syntax error you'll first see something like:
-```
-git commit -m '{message}'
-black....................................................................Failed
-hookid: black
-
-Files were modified by this hook. Additional output:
-
-reformatted this/file/was/reformatted.py
-All done! ✨ 🍰 ✨
-1 file reformatted.
-
-Flake8...................................................................Failed
-hookid: flake8
-
-this/file/was/reformatted.py:{line}:{character}: {what was incorrect}
-```
-After which you can add these changes and commit again. Note that failing pre-commit commands mean that the commit has not taken place: you must commit again!
 
 ## Release process