[SLO] fix typo (#2129)

Co-authored-by: ci.datadog-api-spec <[email protected]> a689b05

datadog_api_client.v1.model.html

@@ -17105,7 +17105,7 @@ <h2 id="submodules">Submodules<a class="headerlink" href="#submodules" title="Li
 as an integer in Unix epoch format in the first element, and the state as an integer in the
 second element. An integer value of <code class="docutils literal notranslate"><span class="pre">0</span></code> for state means uptime, <code class="docutils literal notranslate"><span class="pre">1</span></code> means downtime, and <code class="docutils literal notranslate"><span class="pre">2</span></code> means no data.
 Periods of no data are counted either as uptime or downtime depending on monitor settings.
-See <a class="reference external" href="https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data">SLO documentatio</a>
+See <a class="reference external" href="https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data">SLO documentation</a>
 for detailed information.</p></li>
 <li><p><strong>monitor_modified</strong> (<em>int</em><em>, </em><em>optional</em>) – For <code class="docutils literal notranslate"><span class="pre">monitor</span></code> based SLOs, this is the last modified timestamp in epoch seconds of the monitor.</p></li>
 <li><p><strong>monitor_type</strong> (<em>str</em><em>, </em><em>optional</em>) – For <code class="docutils literal notranslate"><span class="pre">monitor</span></code> based SLOs, this describes the type of monitor.</p></li>
@@ -17219,14 +17219,15 @@ <h2 id="submodules">Submodules<a class="headerlink" href="#submodules" title="Li
 <li><p><strong>error_budget_remaining</strong> (<a class="reference internal" href="#datadog_api_client.v1.model.slo_error_budget_remaining_data.SLOErrorBudgetRemainingData" title="datadog_api_client.v1.model.slo_error_budget_remaining_data.SLOErrorBudgetRemainingData"><em>SLOErrorBudgetRemainingData</em></a><em>, </em><em>optional</em>) – A mapping of threshold <code class="docutils literal notranslate"><span class="pre">timeframe</span></code> to the remaining error budget.</p></li>
 <li><p><strong>errors</strong> (<em>[</em><a class="reference internal" href="#datadog_api_client.v1.model.slo_history_response_error_with_type.SLOHistoryResponseErrorWithType" title="datadog_api_client.v1.model.slo_history_response_error_with_type.SLOHistoryResponseErrorWithType"><em>SLOHistoryResponseErrorWithType</em></a><em>]</em><em>, </em><em>optional</em>) – An array of error objects returned while querying the history data for the service level objective.</p></li>
 <li><p><strong>group</strong> (<em>str</em><em>, </em><em>optional</em>) – For groups in a grouped SLO, this is the group name.</p></li>
-<li><p><strong>history</strong> (<em>[</em><em>[</em><em>float</em><em>]</em><em>]</em><em>, </em><em>optional</em>) – The state transition history for <code class="docutils literal notranslate"><span class="pre">monitor</span></code> or <code class="docutils literal notranslate"><span class="pre">time-slice</span></code> SLOs. It is represented as
+<li><p><strong>history</strong> (<em>[</em><em>[</em><em>float</em><em>]</em><em>]</em><em>, </em><em>optional</em>) – <p>The state transition history for <code class="docutils literal notranslate"><span class="pre">monitor</span></code> or <code class="docutils literal notranslate"><span class="pre">time-slice</span></code> SLOs. It is represented as
 an array of pairs. Each pair is an array containing the timestamp of the transition
 as an integer in Unix epoch format in the first element, and the state as an integer in the
 second element. An integer value of <code class="docutils literal notranslate"><span class="pre">0</span></code> for state means uptime, <code class="docutils literal notranslate"><span class="pre">1</span></code> means downtime, and <code class="docutils literal notranslate"><span class="pre">2</span></code> means no data.
 Periods of no data count as uptime in time-slice SLOs, while for monitor SLOs, no data is counted
 either as uptime or downtime depending on monitor settings. See
 <a class="reference external" href="https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data">SLO documentation</a>
-for detailed information.</p></li>
+for detailed information.</p>
+</p></li>
 <li><p><strong>monitor_modified</strong> (<em>int</em><em>, </em><em>optional</em>) – For <code class="docutils literal notranslate"><span class="pre">monitor</span></code> based SLOs, this is the last modified timestamp in epoch seconds of the monitor.</p></li>
 <li><p><strong>monitor_type</strong> (<em>str</em><em>, </em><em>optional</em>) – For <code class="docutils literal notranslate"><span class="pre">monitor</span></code> based SLOs, this describes the type of monitor.</p></li>
 <li><p><strong>name</strong> (<em>str</em><em>, </em><em>optional</em>) – For groups in a grouped SLO, this is the group name. For monitors in a multi-monitor SLO, this is the monitor name.</p></li>