Update dry-run page

ptarmiganlabs · Jan 8, 2024 · f9f813b · f9f813b
1 parent 37b4ca8
commit f9f813b
Show file tree

Hide file tree

Showing 7 changed files with 33 additions and 32 deletions.
diff --git a/content/en/docs/getting-started/dry-runs/_index.md b/content/en/docs/getting-started/dry-runs/_index.md
@@ -1,16 +1,17 @@
 ---
 title: Dry runs
 description: >
-    Dry-runs are a good idea
+    Dry-runs are a good idea!
 tags: []
 weight: 50
 ---
 
-Many of Ctrl-Q's commands will create, update or delete things in Sense.  
-As long as you have specified the correct parameters that's all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong ones) resources in Sense to be affected.
+Many of Ctrl-Q's commands will create, update or delete things in Sense.
+
+As long as you have specified the correct parameters that's all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong) resources in Sense to be affected.
 
 Most Ctrl-Q commands that change things in Sense have a `--dry-run` option.  
-If it is used, Ctrl-Q will not make any changes in Sense, but instead only show what _would_ happen.
+If used, Ctrl-Q will not make any changes in Sense, but instead only show what _would_ happen.
 
 It's thus a _very_ good idea to first do a dry run of the intended command, verify that the correct things would happen and then finally do a real execution of the desired Ctrl-Q command.
 

diff --git a/docs/docs/_print/index.html b/docs/docs/_print/index.html
@@ -907,11 +907,11 @@ <h2 id="macos-and-linux">macOS and Linux</h2>
 <div class="td-content" style="page-break-before: always">
 
 	<h1 id="pg-0083d5504272cfca0129ce670b9461cd">2.4 - Dry runs</h1>
-    <div class="lead">Dry-runs are a good idea</div>
-	<p>Many of Ctrl-Q&rsquo;s commands will create, update or delete things in Sense.<br>
-As long as you have specified the correct parameters that&rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong ones) resources in Sense to be affected.</p>
+    <div class="lead">Dry-runs are a good idea!</div>
+	<p>Many of Ctrl-Q&rsquo;s commands will create, update or delete things in Sense.</p>
+<p>As long as you have specified the correct parameters that&rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong) resources in Sense to be affected.</p>
 <p>Most Ctrl-Q commands that change things in Sense have a <code>--dry-run</code> option.<br>
-If it is used, Ctrl-Q will not make any changes in Sense, but instead only show what <em>would</em> happen.</p>
+If used, Ctrl-Q will not make any changes in Sense, but instead only show what <em>would</em> happen.</p>
 <p>It&rsquo;s thus a <em>very</em> good idea to first do a dry run of the intended command, verify that the correct things would happen and then finally do a real execution of the desired Ctrl-Q command.</p>
 <p>Might take a bit of extra time, but better safe than sorry.</p>
 

diff --git a/docs/docs/getting-started/_print/index.html b/docs/docs/getting-started/_print/index.html
@@ -447,11 +447,11 @@ <h2 id="macos-and-linux">macOS and Linux</h2>
 <div class="td-content" style="page-break-before: always">
 
 	<h1 id="pg-0083d5504272cfca0129ce670b9461cd">4 - Dry runs</h1>
-    <div class="lead">Dry-runs are a good idea</div>
-	<p>Many of Ctrl-Q&rsquo;s commands will create, update or delete things in Sense.<br>
-As long as you have specified the correct parameters that&rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong ones) resources in Sense to be affected.</p>
+    <div class="lead">Dry-runs are a good idea!</div>
+	<p>Many of Ctrl-Q&rsquo;s commands will create, update or delete things in Sense.</p>
+<p>As long as you have specified the correct parameters that&rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong) resources in Sense to be affected.</p>
 <p>Most Ctrl-Q commands that change things in Sense have a <code>--dry-run</code> option.<br>
-If it is used, Ctrl-Q will not make any changes in Sense, but instead only show what <em>would</em> happen.</p>
+If used, Ctrl-Q will not make any changes in Sense, but instead only show what <em>would</em> happen.</p>
 <p>It&rsquo;s thus a <em>very</em> good idea to first do a dry run of the intended command, verify that the correct things would happen and then finally do a real execution of the desired Ctrl-Q command.</p>
 <p>Might take a bit of extra time, but better safe than sorry.</p>
 

diff --git a/docs/docs/getting-started/dry-runs/_print/index.html b/docs/docs/getting-started/dry-runs/_print/index.html
@@ -20,18 +20,18 @@
 <link rel="icon" type="image/png" href="/favicons/android-192x192.png" sizes="192x192">
 
 <title>Dry runs | Ctrl-Q</title>
-<meta name="description" content="Dry-runs are a good idea
+<meta name="description" content="Dry-runs are a good idea!
 ">
 <meta property="og:title" content="Dry runs" />
-<meta property="og:description" content="Dry-runs are a good idea
+<meta property="og:description" content="Dry-runs are a good idea!
 " />
 <meta property="og:type" content="website" />
 <meta property="og:url" content="https://ctrl-q.ptarmiganlabs.com/docs/getting-started/dry-runs/" /><meta property="og:site_name" content="Ctrl-Q" />
 
 <meta itemprop="name" content="Dry runs">
-<meta itemprop="description" content="Dry-runs are a good idea
+<meta itemprop="description" content="Dry-runs are a good idea!
 "><meta name="twitter:card" content="summary"/><meta name="twitter:title" content="Dry runs"/>
-<meta name="twitter:description" content="Dry-runs are a good idea
+<meta name="twitter:description" content="Dry-runs are a good idea!
 "/>
 
 
@@ -90,7 +90,7 @@
 
 
 <h1 class="title">Dry runs</h1>
-<div class="lead">Dry-runs are a good idea</div>
+<div class="lead">Dry-runs are a good idea!</div>
 
 
 
@@ -108,10 +108,10 @@ <h1 class="title">Dry runs</h1>
 
 
 <div class="content">
-      <p>Many of Ctrl-Q&rsquo;s commands will create, update or delete things in Sense.<br>
-As long as you have specified the correct parameters that&rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong ones) resources in Sense to be affected.</p>
+      <p>Many of Ctrl-Q&rsquo;s commands will create, update or delete things in Sense.</p>
+<p>As long as you have specified the correct parameters that&rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong) resources in Sense to be affected.</p>
 <p>Most Ctrl-Q commands that change things in Sense have a <code>--dry-run</code> option.<br>
-If it is used, Ctrl-Q will not make any changes in Sense, but instead only show what <em>would</em> happen.</p>
+If used, Ctrl-Q will not make any changes in Sense, but instead only show what <em>would</em> happen.</p>
 <p>It&rsquo;s thus a <em>very</em> good idea to first do a dry run of the intended command, verify that the correct things would happen and then finally do a real execution of the desired Ctrl-Q command.</p>
 <p>Might take a bit of extra time, but better safe than sorry.</p>
 

diff --git a/docs/docs/getting-started/dry-runs/index.html b/docs/docs/getting-started/dry-runs/index.html
@@ -20,18 +20,18 @@
 <link rel="icon" type="image/png" href="/favicons/android-192x192.png" sizes="192x192">
 
 <title>Dry runs | Ctrl-Q</title>
-<meta name="description" content="Dry-runs are a good idea
+<meta name="description" content="Dry-runs are a good idea!
 ">
 <meta property="og:title" content="Dry runs" />
-<meta property="og:description" content="Dry-runs are a good idea
+<meta property="og:description" content="Dry-runs are a good idea!
 " />
 <meta property="og:type" content="website" />
 <meta property="og:url" content="https://ctrl-q.ptarmiganlabs.com/docs/getting-started/dry-runs/" /><meta property="og:site_name" content="Ctrl-Q" />
 
 <meta itemprop="name" content="Dry runs">
-<meta itemprop="description" content="Dry-runs are a good idea
+<meta itemprop="description" content="Dry-runs are a good idea!
 "><meta name="twitter:card" content="summary"/><meta name="twitter:title" content="Dry runs"/>
-<meta name="twitter:description" content="Dry-runs are a good idea
+<meta name="twitter:description" content="Dry-runs are a good idea!
 "/>
 
 
@@ -200,14 +200,14 @@ <h5 class="taxonomy-title">Tags</h5>
 
 <div class="td-content">
 	<h1>Dry runs</h1>
-  <div class="lead">Dry-runs are a good idea</div>
+  <div class="lead">Dry-runs are a good idea!</div>
 	<header class="article-meta">
 
   </header>
-	<p>Many of Ctrl-Q&rsquo;s commands will create, update or delete things in Sense.<br>
-As long as you have specified the correct parameters that&rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong ones) resources in Sense to be affected.</p>
+	<p>Many of Ctrl-Q&rsquo;s commands will create, update or delete things in Sense.</p>
+<p>As long as you have specified the correct parameters that&rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong) resources in Sense to be affected.</p>
 <p>Most Ctrl-Q commands that change things in Sense have a <code>--dry-run</code> option.<br>
-If it is used, Ctrl-Q will not make any changes in Sense, but instead only show what <em>would</em> happen.</p>
+If used, Ctrl-Q will not make any changes in Sense, but instead only show what <em>would</em> happen.</p>
 <p>It&rsquo;s thus a <em>very</em> good idea to first do a dry run of the intended command, verify that the correct things would happen and then finally do a real execution of the desired Ctrl-Q command.</p>
 <p>Might take a bit of extra time, but better safe than sorry.</p>
 

diff --git a/docs/docs/getting-started/index.html b/docs/docs/getting-started/index.html
@@ -263,7 +263,7 @@ <h5>
                 <h5>
                     <a href="/docs/getting-started/dry-runs/">Dry runs</a>
                 </h5>
-                <p>Dry-runs are a good idea</p>
+                <p>Dry-runs are a good idea!</p>
             </div>
 
 

diff --git a/docs/docs/getting-started/index.xml b/docs/docs/getting-started/index.xml
@@ -204,10 +204,10 @@ The only difference is that you don&amp;rsquo;t have to install a new command li
       <description>
 
 
-        &lt;p&gt;Many of Ctrl-Q&amp;rsquo;s commands will create, update or delete things in Sense.&lt;br&gt;
-As long as you have specified the correct parameters that&amp;rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong ones) resources in Sense to be affected.&lt;/p&gt;
+        &lt;p&gt;Many of Ctrl-Q&amp;rsquo;s commands will create, update or delete things in Sense.&lt;/p&gt;
+&lt;p&gt;As long as you have specified the correct parameters that&amp;rsquo;s all good - but there is also the risk of using incorrect parameters or filters, causing too many (or too few or the wrong) resources in Sense to be affected.&lt;/p&gt;
 &lt;p&gt;Most Ctrl-Q commands that change things in Sense have a &lt;code&gt;--dry-run&lt;/code&gt; option.&lt;br&gt;
-If it is used, Ctrl-Q will not make any changes in Sense, but instead only show what &lt;em&gt;would&lt;/em&gt; happen.&lt;/p&gt;
+If used, Ctrl-Q will not make any changes in Sense, but instead only show what &lt;em&gt;would&lt;/em&gt; happen.&lt;/p&gt;
 &lt;p&gt;It&amp;rsquo;s thus a &lt;em&gt;very&lt;/em&gt; good idea to first do a dry run of the intended command, verify that the correct things would happen and then finally do a real execution of the desired Ctrl-Q command.&lt;/p&gt;
 &lt;p&gt;Might take a bit of extra time, but better safe than sorry.&lt;/p&gt;