Merge pull request #17958 from newrelic/clark/fix-file-for-translation

fix: replace DoNotTranslate with DNT

src/content/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions.mdx

@@ -40,7 +40,7 @@ For some [types of conditions](#requirements), you can create a description temp
 * Define next steps
 * Add metadata to downstream systems
 
-The <DoNotTranslate>**Description template**</DoNotTranslate> field allows you to use a general template structure that, when an incident is generated, substitutes the generic sections with specific values. For example, let's say you used this in a description:
+The <DNT>**Description template**</DNT> field allows you to use a general template structure that, when an incident is generated, substitutes the generic sections with specific values. For example, let's say you used this in a description:
 
 ```handlebars
 This is my condition name : {{conditionName}}
@@ -63,7 +63,7 @@ The hostname is : ip-123-45-67-89.us-west-1.compute.internal
 />
 
 <figcaption>
-  <DoNotTranslate>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (Policies) > (select a policy) > (select a condition)**</DoNotTranslate>: Click <DoNotTranslate>**+ Add description template**</DoNotTranslate> to open the field.
+  <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (Policies) > (select a policy) > (select a condition)**</DNT>: Click <DNT>**+ Add description template**</DNT> to open the field.
 </figcaption>
 
 You can create a description template using [the dedicated field for NRQL alerts](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions/), or the [Describe this condition section for infrastructure alerts](/docs/infrastructure/new-relic-infrastructure/infrastructure-alert-conditions/infrastructure-alerts-add-edit-or-view-host-alert-information/).
@@ -102,13 +102,13 @@ The attributes you can use in a description template are a subset of attributes
   ```
 * Tag attributes: For tags, you would use the format `{{tag.TAG_NAME}}`. There are two types of tags:
 
-  * Entity-related tags: <DoNotTranslate>**For infrastructure conditions only.**</DoNotTranslate> You can find available [entity-related tags](/docs/new-relic-one/use-new-relic-one/core-concepts/tagging-use-tags-organize-group-what-you-monitor#) by going to the [entity explorer](/docs/new-relic-one/use-new-relic-one/ui-data/new-relic-one-entity-explorer-view-performance-across-apps-services-hosts) and looking under a service's <DoNotTranslate>**Metadata and tags**</DoNotTranslate>, or by viewing incident details. Here's an example of using tags in a description template:
+  * Entity-related tags: <DNT>**For infrastructure conditions only.**</DNT> You can find available [entity-related tags](/docs/new-relic-one/use-new-relic-one/core-concepts/tagging-use-tags-organize-group-what-you-monitor#) by going to the [entity explorer](/docs/new-relic-one/use-new-relic-one/ui-data/new-relic-one-entity-explorer-view-performance-across-apps-services-hosts) and looking under a service's <DNT>**Metadata and tags**</DNT>, or by viewing incident details. Here's an example of using tags in a description template:
 
     ```handlebars
     The AWS region is : {{tag.aws.awsRegion}}
     Responsible team : {{tag.label.owning_team}}
     ```
-  * Facet clause tags: <DoNotTranslate>**For NRQL conditions only.**</DoNotTranslate> If a NRQL condition uses a `FACET` clause, you can use `tag` formatting to use those values in your description template. For example, if the NRQL query included `FACET hostName, cluster`, you could then use this:
+  * Facet clause tags: <DNT>**For NRQL conditions only.**</DNT> If a NRQL condition uses a `FACET` clause, you can use `tag` formatting to use those values in your description template. For example, if the NRQL query included `FACET hostName, cluster`, you could then use this:
 
     ```handlebars
     The host is : {{tag.hostName}}
@@ -155,7 +155,7 @@ mutation {
 
 ## Mentioning users or notifying channel in Slack [#mention-in-slack]
 
-When creating a description that you know will be sent to [Slack](/docs/alerts-applied-intelligence/new-relic-alerts/alert-notifications/notification-channels-control-where-send-alerts#slack), you may wish to <DoNotTranslate>**@mention**</DoNotTranslate> a user or generate a channel-wide notification (for example, <DoNotTranslate>**@here**</DoNotTranslate> or <DoNotTranslate>**@channel**</DoNotTranslate>). To achieve this, simply include the User ID or a channel-wide notification in the description surrounded by `<` and `>` characters.
+When creating a description that you know will be sent to [Slack](/docs/alerts-applied-intelligence/new-relic-alerts/alert-notifications/notification-channels-control-where-send-alerts#slack), you may wish to <DNT>**@mention**</DNT> a user or generate a channel-wide notification (for example, <DNT>**@here**</DNT> or <DNT>**@channel**</DNT>). To achieve this, simply include the User ID or a channel-wide notification in the description surrounded by `<` and `>` characters.
 
 Here's an example for mentioning a user: