Consistent heading levels

Author: MisRob

docs/howtos/development_with_kds.md

@@ -1,4 +1,4 @@
-## Running Kolibri with local Kolibri Design System
+# Running Kolibri with local Kolibri Design System
 
 Kolibri uses components from [Kolibri Design System](https://github.com/learningequality/kolibri-design-system) (KDS). KDS is installed in Kolibri as a usual npm dependency.
 

docs/howtos/installing_pyenv.md

@@ -1,10 +1,10 @@
-## Installing pyenv
+# Installing pyenv
 
-### Prerequisites
+## Prerequisites
 
 [Git](https://git-scm.com/) installed.
 
-### Install
+## Install
 
 First check to see if you already have `pyenv` installed by running this in a terminal window:
 
@@ -91,7 +91,7 @@ The output of the command tells you to add certain lines to your startup files f
 
   **Proxy note**: If you use a proxy, export `http_proxy` and `https_proxy`, too.
 
-### Installation of pyenv on Windows
+## Installation of pyenv on Windows
 
 1. Run PowerShell terminal as Administrator
 2. Run the following installation command in the PowerShell terminal :
@@ -110,7 +110,7 @@ press Y not A, to execute Policy Change for this power shell only.
 
 then run the previous command again
 
-### Restart your shell
+## Restart your shell
 
 For the `PATH` changes to take effect, run the following command.
 
@@ -124,13 +124,13 @@ To check if pyenv is installed correctly, type:
 
   `pyenv version`
 
-### Install Python build dependencies
+## Install Python build dependencies
 
 [**Install Python build dependencies**](https://github.com/pyenv/pyenv/wiki#suggested-build-environment) before attempting to install a new Python version.
 
 You can now begin using Pyenv.
 
-### Installing a Python Version with PyEnv
+## Installing a Python Version with PyEnv
 
 Use the `pyenv` command in your terminal to install a recent version of Python:
 

docs/howtos/pyenv_virtualenv.md

@@ -1,10 +1,10 @@
-## Using pyenv-virtualenv
+# Using pyenv-virtualenv
 
-### Virtual Environments
+## Virtual Environments
 
 Virtual environments allow a developer to have an encapsulated Python environment, using a specific version of Python, and with dependencies installed in a way that only affect the virtual environment. This is important as different projects or even different versions of the same project may have different dependencies, and virtual environments allow you to switch between them seamlessly and explicitly.
 
-### Using `pyenv virtualenv` with pyenv
+## Using `pyenv virtualenv` with pyenv
 
 To create a virtualenv for the Python version used with pyenv, run `pyenv virtualenv`, specifying the Python version you want and the name of the virtualenv directory. For example, because we can make a virtual environment for Kolibri using Python 3.9.9:
 
@@ -17,7 +17,7 @@ If you get 'command not found' or a similar error, and pyenv virtualenv is not i
 will create a virtualenv based on Python 3.9.9 under `$(pyenv root)/versions` in a
 folder called `kolibri-py3.9`.
 
-### List existing virtualenvs
+## List existing virtualenvs
 
 `pyenv virtualenvs` shows you the list of existing virtualenvs and `conda` environments.
 
@@ -30,7 +30,7 @@ $ pyenv virtualenvs
 There are two entries for each virtualenv, and the shorter one is just a symlink.
 
 
-### Activate virtualenv
+## Activate virtualenv
 
 If you want a virtual environment to always activate when you enter a certain directory, you can use the [`pyenv local`](https://github.com/pyenv/pyenv/blob/master/COMMANDS.md#pyenv-local) command.
 
@@ -47,7 +47,7 @@ pyenv activate kolibri-py3.9
 pyenv deactivate
 ```
 
-### Delete existing virtualenv
+## Delete existing virtualenv
 
 Removing the directories in `$(pyenv root)/versions` and `$(pyenv root)/versions/{version}/envs` will delete the virtualenv, or you can run:
 

docs/howtos/rebasing_a_pull_request.md

@@ -1,4 +1,4 @@
-## Rebasing a Pull Request
+# Rebasing a Pull Request
 
 On certain occasions, it might be necessary to redirect a pull request from the develop branch to the latest release branch, such as `release-v*` (e.g., `release-v0.16.x` when working on version 0.16), or vice versa. This guide outlines the steps for rebasing a feature branch related to your pull request while maintaining a clean commit history.