deploy: 59279b816d

en/post-install.html

@@ -163,15 +163,6 @@ echo "version = '${version:?}'" > ~/.config/xplr/init.lua
 <p>Then
 <strong><a href="https://github.com/sayanarijit/xplr/blob/main/src/init.lua">copy from here</a></strong>
 and remove / comment out what you don't want to customize.</p>
-<blockquote>
-<p><strong>Note:</strong> You don't generally need to create the config file. You can use the
-default configuration for basic operations. However, creating the config file
-is recommended because the project is in its early stage and the defaults
-might change. Creating the config file will save you from unexpected behavior
-when you <a href="upgrade-guide.html">upgrade</a>.
-Also, the default configuration is meant to be overwritten to suit your
-workflow.</p>
-</blockquote>
 <h2 id="run"><a class="header" href="#run">Run</a></h2>
 <pre><code>xplr
 </code></pre>

en/print.html

@@ -414,15 +414,6 @@ echo "version = '${version:?}'" > ~/.config/xplr/init.lua
 <p>Then
 <strong><a href="https://github.com/sayanarijit/xplr/blob/main/src/init.lua">copy from here</a></strong>
 and remove / comment out what you don't want to customize.</p>
-<blockquote>
-<p><strong>Note:</strong> You don't generally need to create the config file. You can use the
-default configuration for basic operations. However, creating the config file
-is recommended because the project is in its early stage and the defaults
-might change. Creating the config file will save you from unexpected behavior
-when you <a href="upgrade-guide.html">upgrade</a>.
-Also, the default configuration is meant to be overwritten to suit your
-workflow.</p>
-</blockquote>
 <h2 id="run"><a class="header" href="#run">Run</a></h2>
 <pre><code>xplr
 </code></pre>