Update Documentation

astarte/1.2/010-astarte_in_5_minutes.html

@@ -105,7 +105,7 @@ <h1>
   <span>Astarte in 5 minutes</span>
 </h1>
 
-<p><strong>This documentation page describes a development version, for production systems please use the <a href="https://docs.astarte-platform.org/latest">stable version</a> instead.</strong></p><p>This tutorial will guide you through bringing up your Astarte instance, creating a realm and streaming your first data from a device simulator (or a real device) before your cup of tea is ready.</p><h2 id="before-you-begin" class="section-heading">
+<p>This tutorial will guide you through bringing up your Astarte instance, creating a realm and streaming your first data from a device simulator (or a real device) before your cup of tea is ready.</p><h2 id="before-you-begin" class="section-heading">
   <a href="#before-you-begin" class="hover-link"><i class="ri-link-m" aria-hidden="true"></i>
   <p class="sr-only">before-you-begin</p>
   </a>

astarte/1.2/062-trigger_delivery_policies.html

@@ -126,7 +126,7 @@ <h1>
 This is a required component and uniquely identifies the policy in the realm.</p></li><li><p>Error handlers: a non-empty list of handlers. 
 Each handler acts on groups of delivery errors and describes the strategy Astarte should take when they occur.
 In pseudo-BNF syntax, an handler is described by the following grammar:</p><pre><code class="makeup elixir" translate="no"><span class="w">    </span><span class="n">handler</span><span class="w"> </span><span class="o">::</span><span class="o">=</span><span class="w"> </span><span class="s">&quot;{&quot;</span><span class="w">
-        </span><span class="s">&quot;on&quot;</span><span class="w"> </span><span class="s">&quot;:&quot;</span><span class="w"> </span><span class="s">&quot;client_error&quot;</span><span class="w"> </span><span class="o">|</span><span class="w"> </span><span class="s">&quot;server_error&quot;</span><span class="w"> </span><span class="o">|</span><span class="w"> </span><span class="s">&quot;any_error&quot;</span><span class="w"> </span><span class="o">|</span><span class="w"> </span><span class="p" data-group-id="5989496645-1">[</span><span class="o">&lt;</span><span class="n">int</span><span class="o">&gt;</span><span class="p" data-group-id="5989496645-1">]</span><span class="w"> </span><span class="s">&quot;,&quot;</span><span class="w">
+        </span><span class="s">&quot;on&quot;</span><span class="w"> </span><span class="s">&quot;:&quot;</span><span class="w"> </span><span class="s">&quot;client_error&quot;</span><span class="w"> </span><span class="o">|</span><span class="w"> </span><span class="s">&quot;server_error&quot;</span><span class="w"> </span><span class="o">|</span><span class="w"> </span><span class="s">&quot;any_error&quot;</span><span class="w"> </span><span class="o">|</span><span class="w"> </span><span class="p" data-group-id="3098390675-1">[</span><span class="o">&lt;</span><span class="n">int</span><span class="o">&gt;</span><span class="p" data-group-id="3098390675-1">]</span><span class="w"> </span><span class="s">&quot;,&quot;</span><span class="w">
         </span><span class="s">&quot;strategy&quot;</span><span class="w"> </span><span class="s">&quot;:&quot;</span><span class="w"> </span><span class="s">&quot;discard&quot;</span><span class="w"> </span><span class="o">|</span><span class="w"> </span><span class="s">&quot;retry&quot;</span><span class="w">
     </span><span class="s">&quot;}&quot;</span></code></pre><p>There are two possible strategies: either discard the event or retry. If the strategy is <code class="inline">retry</code>, events will be requeued in the event queue.
 The default retry strategy is discarding events.

astarte/1.2/search.html

@@ -102,7 +102,7 @@ <h1>
 
   <div class="loading"><div></div><div></div><div></div><div></div></div>
 </div>
-<script src="dist/search_items-BD27FAF1.js"></script>
+<script src="dist/search_items-8EDBF5DF.js"></script>
       <footer class="footer">
 
         <p>