[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Author: pre-commit-ci[bot]

docs/guides/environments.md

@@ -29,6 +29,7 @@ One of the easiest ways to mess up a conda installation is to install a bunch of
 ## Install *micromamba*
 
 ### Run the installer
+
 Install `micromamba`, the executable we will use to manage our virtual environments.
 
 === "MacOS/Linux"
@@ -39,19 +40,19 @@ Install `micromamba`, the executable we will use to manage our virtual environme
     ```console
     $ "${SHELL}" <(curl -L micro.mamba.pm/install.sh)
     ---> 100%
-    
+
     // You will be asked whether you want to initialise your shell.
     // Respond "Y".
-    
+
     Init shell? [Y/n] Y
-    
+
     // You will be asked where you want to install micromamba.
     // Using the default is recommended.
-    
+
     Prefix location? [~/micromamba]
-    
+
     // You will need to restart your shell for changes to take effect.
-    
+
     Please restart your shell to activate micromamba.
     ```
 
@@ -60,26 +61,26 @@ Install `micromamba`, the executable we will use to manage our virtual environme
     Next, setup `micromamba` to download packages from
     [*conda-forge*](https://conda-forge.org/)
     a community driven package repository.
-    
+
     <div class="termy">
-        
+
     ```console
     $ micromamba config append channels conda-forge
     $ micromamba config append channels nodefaults
     $ micromamba config set channel_priority strict
     ```
-    
+
     </div>
 
 === "Windows"
 
     todo: add windows guide
-    
-### Set up an alias
+
+###  Set up an alias
 
 !!!tip "set up an alias for micromamba"
     `micromamba` replaces `conda`. Set up an alias if you want to type `conda` at the prompt.
-    
+
 === "bash"
 
     ```bash title="~/.bashrc"
@@ -91,9 +92,9 @@ Install `micromamba`, the executable we will use to manage our virtual environme
     ```zsh title="~/.zshrc"
     alias conda="micromamba"
     ```
-    
+
 === "PowerShell"
-    
+
     ```PowerShell title="$Home\Documents\PowerShell\Microsoft.PowerShell_profile.ps1"
     Set-Alias conda mamba
     ```
@@ -107,45 +108,42 @@ We will use `conda` at the prompt rather than `micromamba` for the rest of this
 Run the following to create and activate an environment called `my-env` with Python 3.10
 
 <div class="termy">
-    
+
     ```console
     $ conda create --name my-env python=3.10
-    
+
     // To work in the environment we first need to activate it.
-    
+
     $ conda activate my-env
-    
+
     // Your prompt will indicate your current environment.
-    
-    $ (my-env) ➜ 
-    
+
+    $ (my-env) ➜
+
     // Let's check that we have the correct Python version.
-    
+
     $ (my-env) ➜ python --version
     Python 3.10.10
-    
+
     ```
 
 </div>
 
-
-
 ### Installing packages
 
 You can install most packages into your environment with `conda` or `pip`.
-Install what you can with `conda`. If a package is available on 
+Install what you can with `conda`. If a package is available on
 [PyPI](https://pypi.org/) but not [conda-forge](https://conda-forge.org/) then use `pip`.
 
 === "conda"
 
     <div class="termy">
-        
+
     ```console
     $ (my-env) ➜ conda install numpy
     ```
 
     </div>
-    
 
 === "pip"
 
@@ -165,9 +163,9 @@ We can deactivate an environment with
 
     ```console
     $ (my-env) ➜ conda deactivate
-    
+
     // You are no longer in my-env.
-    
+
     $
     ```
 
@@ -209,7 +207,7 @@ This is useful for workflows which rely on software with incompatible dependenci
 !!!tip "Get comfy! 🧸"
     Getting comfortable with the creation, destruction, activation and deactivation of environments at will is liberating.
     Practice now!
-    
+
 !!!tip "One environment per project 🌍"
     Working with one environment per project is a useful ideal.
     A general purpose environment can be useful for quick scripts and analysis.