Fix typos

docs/contributing.rst

@@ -27,10 +27,10 @@ To contribute code and/or documentation you should follow this workflow:
 
 1. check the issue tracker on GitHub to see if someone is already working on your idea
 2. open a new issue stating your idea and how you wish to implement it
-2. fork the Zoe repository via Eurecom's GitLab
-3. create a branch that will hold your changes
-4. ... develop and debug ...
-5. when you are ready propose your changes on the mailing list
+3. fork the Zoe repository via Eurecom's GitLab
+4. create a branch that will hold your changes
+5. ... develop and debug ...
+6. when you are ready propose your changes on the mailing list
 
 Zoe maintainers will review your code, give constructive feedback and eventually perform a pull and a merge.
 

docs/users.rst

@@ -19,7 +19,7 @@ Each user has a :ref:`roles` and a :ref:`quotas` associated.
 By default Zoe has an admin user (with password "admin"), created during the first startup. While deploying Zoe, this user must be disabled or its password changed. The default password is a security risk.
 
 Experimental OAuth2 support
---------------------------
+---------------------------
 
 This version of Zoe includes an experimental OAuth2 client implementation that points to a GitLab instance in Eurecom's infrastructure. To use it with your own OAuth2 provider, you need to modify the source code under ``zoe_api/auth/requests_oauth2/services.py``, ``zoe_api/rest_api/user.py`` and ``zoe_api/web/start.py``.