Deployed 9c2d5cd to dev with MkDocs 1.5.3 and mike 2.0.0

dev/features/environment/index.html

@@ -1680,9 +1680,9 @@ <h1 id="environments">Environments<a class="headerlink" href="#environments" tit
 <p>Pixi is a tool to manage virtual environments.
 This document explains what an environment looks like and how to use it.</p>
 <h2 id="structure">Structure<a class="headerlink" href="#structure" title="Permanent link">#</a></h2>
-<p>A pixi environment is located in the <code>.pixi/envs</code> directory of the project.
-This location is <strong>not</strong> configurable as it is a specific design decision to keep the environments in the project directory.
-This keeps your machine and your project clean and isolated from each other, and makes it easy to clean up after a project is done.</p>
+<p>A pixi environment is located in the <code>.pixi/envs</code> directory of the project by default.
+This keeps your machine and your project clean and isolated from each other, and makes it easy to clean up after a project is done.
+While this structure is generally recommended, environments can also be stored outside of project directories by enabling <a href="../../reference/pixi_configuration/#detached-environments">detached environments</a>.</p>
 <p>If you look at the <code>.pixi/envs</code> directory, you will see a directory for each environment, the <code>default</code> being the one that is normally used, if you specify a custom environment the name you specified will be used.</p>
 <div class="language-shell highlight"><pre><span></span><code><span id="__span-0-1"><a id="__codelineno-0-1" name="__codelineno-0-1" href="#__codelineno-0-1"></a>.pixi
 </span><span id="__span-0-2"><a id="__codelineno-0-2" name="__codelineno-0-2" href="#__codelineno-0-2"></a>└──<span class="w"> </span>envs