[SLO] fix typo (#2129)

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

Author: api-clients-generation-pipeline[bot]

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-10-07 20:44:54.911447",
-            "spec_repo_commit": "5b4f9ebe"
+            "regenerated": "2024-10-08 14:16:15.442616",
+            "spec_repo_commit": "eb227ded"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-10-07 20:44:54.925632",
-            "spec_repo_commit": "5b4f9ebe"
+            "regenerated": "2024-10-08 14:16:15.459899",
+            "spec_repo_commit": "eb227ded"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -10843,7 +10843,7 @@ components:
             Periods of no data are counted either as uptime or downtime depending
             on monitor settings.
 
-            See [SLO documentatio](https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data)
+            See [SLO documentation](https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data)
 
             for detailed information.'
           example:

src/datadog_api_client/v1/model/slo_history_monitor.py

@@ -89,7 +89,7 @@ def __init__(
             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 ``0`` for state means uptime, ``1`` means downtime, and ``2`` means no data.
             Periods of no data are counted either as uptime or downtime depending on monitor settings.
-            See `SLO documentatio <https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data>`_
+            See `SLO documentation <https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data>`_
             for detailed information.
         :type history: [[float]], optional