Remove double-spacing (DataDog#17923)

* Removing double-spacing * Revert change to suppress-alert-with-downtimes

Author: hestonhoffman

.vale.ini

@@ -13,7 +13,7 @@ Datadog.Trademarks = YES
 Datadog.abbreviations = NO
 Datadog.americanspelling = NO
 Datadog.dashes = NO
-Datadog.emdash = NO
+Datadog.endash = NO
 Datadog.gender = NO
 Datadog.headings = NO
 Datadog.inclusive = NO

content/en/account_management/audit_trail/_index.md

@@ -49,7 +49,7 @@ To enable Datadog Audit Trail, navigate to your [Organization Settings][2] and s
 To see who enabled Audit Trail:
 1. Navigate to [Events Explorer][3].
 2. Enter `Datadog Audit Trail was enabled by` in the search bar. You may have to select a wider time range to capture the event.
-3.  The most recent event with the title "A user enabled Datadog Audit Trail" shows who last enabled Audit Trail.
+3. The most recent event with the title "A user enabled Datadog Audit Trail" shows who last enabled Audit Trail.
 
 ## Configuration
 

content/en/account_management/billing/apm_tracing_profiler.md

@@ -140,7 +140,7 @@ Kubernetes creates pause containers to acquire the respective pod's IP address a
 
 **6. How is the host billing related to your services?**
 
-APM is billed on the basis of [hosts][4] deployed with agents sending traces and not services.  Additionally, over the monthly allocation by host, APM is billed on the basis of Ingested span volume and Indexed span count. To estimate how many ingested and indexed spans each of your services is sending, see the [ingestion][2] and [retention][13] documentation.
+APM is billed on the basis of [hosts][4] deployed with agents sending traces and not services. Additionally, over the monthly allocation by host, APM is billed on the basis of Ingested span volume and Indexed span count. To estimate how many ingested and indexed spans each of your services is sending, see the [ingestion][2] and [retention][13] documentation.
 
 **7. What happens to your existing App Analytics filters?**
 

content/en/account_management/billing/custom_metrics.md

@@ -298,7 +298,7 @@ You are allocated a certain number of **ingested** and **indexed** custom metric
 
 These allocations are counted across your entire infrastructure. For example, if you are on the Pro plan and licensed for three hosts, 300 indexed custom metrics are allocated. The 300 indexed custom metrics can be divided equally across each host, or all 300 indexed metrics can be used by a single host. Using this example, the graphic below shows scenarios that do not exceed the allocated custom metric count:
 
-{{< img src="account_management/billing/custom_metrics/host_custom_metrics.png" alt="Allocations for Custom Metrics"  >}}
+{{< img src="account_management/billing/custom_metrics/host_custom_metrics.png" alt="Allocations for Custom Metrics" >}}
 
 The billable number of indexed custom metrics is based on the average number of custom metrics (from all paid hosts) per hour over a given month. The billable number of ingested custom metrics only grows if you've used Metrics without Limits™ to configure your metric. Contact [Sales][9] or your [Customer Success][10] Manager to discuss custom metrics for your account or to purchase an additional custom metrics package.
 

content/en/account_management/faq/as-a-parent-account-admin-how-do-i-create-new-sub-organizations.md

@@ -7,6 +7,6 @@ Users can access the [Create New Organization][1] feature in the settings (reach
 
 This feature allows all users with the Org Management (`org_management`) permission in the parent account to create new sub-organizations. New sub-organizations are treated as completely separate entities, allowing users to be part of multiple Datadog organizations, each with data accessible only to users within those organizations.
 
-{{< img src="account_management/faq/mceclip0.png" alt="mceclip0"  >}}
+{{< img src="account_management/faq/mceclip0.png" alt="mceclip0" >}}
 
 [1]: /account_management/multi_organization/

content/en/account_management/faq/help-my-password-email-never-came-through.md

@@ -11,7 +11,7 @@ When attempting to reset your password, check if you previously changed your ema
 
 Confirm this from the team page as shown here:
 
-{{< img src="account_management/faq/handle_image.png" alt="handle image"  >}}
+{{< img src="account_management/faq/handle_image.png" alt="handle image" >}}
 
 Enter your email address using the password reset link:
 

content/en/account_management/org_settings/ip_allowlist.md

@@ -9,7 +9,7 @@ The IP allowlist feature is available for enterprise-level customers only. Reque
 
 ## Overview
 
-{{< img src="account_management/org_settings/ip_allowlist_list.png" alt="Screenshot showing the IP allowlist UI, containing four IP ranges"  >}}
+{{< img src="account_management/org_settings/ip_allowlist_list.png" alt="Screenshot showing the IP allowlist UI, containing four IP ranges" >}}
 
 The IP allowlist controls which networks can be used to access your data in Datadog. By limiting allowed networks, you can protect your resources from data exfiltration and insider threats.
 
@@ -67,7 +67,7 @@ To toggle the IP allowlist status, click the **Enable** or **Disable** button.
 
 ### Add IP addresses or CIDR ranges
 
-{{< img src="account_management/org_settings/add_ip.png" alt="Screenshot showing a dialog box titled Add IP to allowlist"  >}}
+{{< img src="account_management/org_settings/add_ip.png" alt="Screenshot showing a dialog box titled Add IP to allowlist" >}}
 
 1. Click the **Add IP** button at the top right of the page. 
 1. Enter a valid IP address or CIDR range.

content/en/account_management/org_settings/sensitive_data_detection.md

@@ -35,7 +35,7 @@ Sensitive Data Scanner can be found under [Organization Settings][1].
 ### Setup
 
 - **Define Scanning Groups:** A scanning group determines what data to scan. It consists of a query filter and a set of toggles to enable scanning for Logs, APM, RUM, and/or Events. See the [Log Search Syntax][2] documentation to learn more about query filters.
-- **Define Scanning Rules:** A scanning rule determines what sensitive information to match within the data.  Within a scanning group, add predefined scanning rules from Datadog's Scanning Rule Library or create your own rules from scratch to scan using custom regex patterns.
+- **Define Scanning Rules:** A scanning rule determines what sensitive information to match within the data. Within a scanning group, add predefined scanning rules from Datadog's Scanning Rule Library or create your own rules from scratch to scan using custom regex patterns.
 
 Sensitive Data Scanner supports Perl Compatible RegEx (PCRE), but the following patterns are not supported:
  - Backreferences and capturing sub-expressions (lookarounds)
@@ -67,7 +67,7 @@ Sensitive Data Scanner supports Perl Compatible RegEx (PCRE), but the following
 ### Out-of-the-box Scanning Rules
 
 The Scanning Rule Library contains an evergrowing collection of predefined rules maintained by Datadog for detecting common patterns such as email addresses, credit card numbers, API keys, authorization tokens, and more.
-{{< img src="logs/sensitive_data_scanner/sds-library-28-03-23.png" alt="Scanning Rule Library"  style="width:90%;">}}
+{{< img src="logs/sensitive_data_scanner/sds-library-28-03-23.png" alt="Scanning Rule Library" style="width:90%;">}}
 
 ### Permissions
 

content/en/account_management/saml/_index.md

@@ -41,14 +41,14 @@ Configuring [SAML (Security Assertion Markup Language)][1] for your Datadog acco
 4. Download Datadog's [Service Provider metadata][18] to configure your IdP to recognize Datadog as a Service Provider.
 
 5. After you upload the IdP Meta-data and configure your IdP, enable SAML in Datadog by clicking the **Upload and Enable** button.
- {{< img src="account_management/saml/saml_enable.png" alt="saml enable"  >}}
+ {{< img src="account_management/saml/saml_enable.png" alt="saml enable" >}}
 
 6. After uploading the IdP metadata, return to the **Login Methods** page and turn SAML `on` by default. 
 
 7. Once SAML is configured in Datadog and your IdP is set up to accept requests from Datadog, users can log in:
 
  - **If using SP-initiated login** (Service Provider, or login initiated from Datadog): By using the **Single Sign-on URL** shown in the Status box at the top of the [SAML Configuration page][19]. The **Single Sign-on URL** is also displayed on the [Team page][20]. Loading this URL initiates a SAML authentication against your IdP. **Note**: This URL isn't displayed unless SAML is enabled for your account and you are using SP-initiated login.
- {{< img src="account_management/saml/saml_enabled.png" alt="Saml Enabled"  >}}
+ {{< img src="account_management/saml/saml_enabled.png" alt="Saml Enabled" >}}
 
  - **If using IdP-initiated login** (Identity Provider, or login initiated from your app portal): By clicking on the app icon in your app portal, for example in the Google App drawer or the Okta App Portal. In some scenarios users logging in with the SP-initiated login URL will also work with the IdP-initiated login experiences, but this depends on your Identity Provider's configuration and support.
 
@@ -107,7 +107,7 @@ It's important to understand what is sent in an assertion before turning on mapp
 
  For example, if you want all users whose `member_of` attribute has a value of `Development` to be assigned to a custom Datadog role called `Devs`:
 
- {{< img src="account_management/saml/create_mapping.png" alt="Creating a SAML mapping to Datadog Role"  >}}
+ {{< img src="account_management/saml/create_mapping.png" alt="Creating a SAML mapping to Datadog Role" >}}
 
  **Note**: Every identity provider is different. Some allow you to set your attribute key or label. Others provide one by default. Datadog recommends you use an assertion inspector on your login to view the details of your particular assertion to understand how your Identity Provider is sending your group membership.
 

content/en/agent/faq/how-datadog-agent-determines-the-hostname.md

@@ -52,7 +52,7 @@ The names collected by the Agent (detailed above) are added as aliases for the c
 
 See the list of all hosts in your account from the [Infrastructure List][4]. The aliases associated with each host are available in the inspect panel, which is accessed by clicking the **Inspect** button while hovering over a host row:
 
-{{< img src="agent/faq/host_aliases.png" alt="Host aliases"  >}}
+{{< img src="agent/faq/host_aliases.png" alt="Host aliases" >}}
 
 **Note**: These aliases are not available for searching or filtering. They are available only in the inspect panel mentioned above.
 
@@ -119,7 +119,7 @@ If you're upgrading from Agent v5 with `gce_updated_hostname` unset or set to fa
 {{% /tab %}}
 {{% tab "Agent v5" %}}
 
-{{< img src="agent/faq/agent_hostname.jpeg" alt="Agent hostname scheme"  >}}
+{{< img src="agent/faq/agent_hostname.jpeg" alt="Agent hostname scheme" >}}
 
 {{% /tab %}}
 {{< /tabs >}}