chore: bring develop, resolve merge conflicts, update 3 files that fa…

…iled mdx verify

src/content/docs/accounts/accounts-billing/account-setup/choose-your-data-center.mdx

@@ -46,7 +46,7 @@ New Relic offers almost all the same active products, features, support offering
 * [Log patterns](/docs/logs/log-management/ui-data/find-unusual-logs-log-patterns/#availability)
 * Deprecated products and features are not available.
 
-[New Relic's Incident Intelligence](/docs/new-relic-one/use-new-relic-one/new-relic-ai/get-started-incident-intelligence) service operates solely in the US whether you store your data in New Relic’s US region data center or New Relic’s EU region data center, by using New Relic Incident Intelligence, you consent that New Relic may move and store your data in the US region.
+[New Relic's incident intelligence](/docs/new-relic-one/use-new-relic-one/new-relic-ai/get-started-incident-intelligence) service operates solely in the US whether you store your data in New Relic’s US region data center or New Relic’s EU region data center, by using New Relic incident intelligence, you consent that New Relic may move and store your data in the US region.
 
 [New Relic CodeStream](/docs/codestream/start-here/what-is-codestream) operates solely in the US. Whether you have selected New Relic's US or EU region data center during setup of your New Relic account, when using New Relic CodeStream, you consent that your New Relic CodeStream data will get stored in the US.
 

src/content/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model.mdx

@@ -805,7 +805,7 @@ Users in a [parent account](/docs/accounts/original-accounts-billing/original-us
 
     <tr>
       <td>
-        Add, update, and delete Proactive Detection configurations.
+        Add, update, and delete proactive detection configurations.
       </td>
 
       <td className="fcenter">

src/content/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/change-applied-intelligence-correlation-logic-decisions.mdx

@@ -1,6 +1,6 @@
 ---
-title: Change Applied Intelligence correlation logic with decisions
-metaDescription: "For New Relic's Applied Intelligence, how to configure the correlation logic using decisions."
+title: Change applied intelligence correlation logic with decisions
+metaDescription: "For New Relic's applied intelligence, how to configure the correlation logic using decisions."
 redirects: 
   - /docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/best-practices-ai-decisions/
   - /docs/new-relic-one/use-new-relic-one/new-relic-ai/get-started-decisions/
@@ -21,30 +21,30 @@ import topology2 from 'images/topology-2.png'
 
 import topology3 from 'images/topology-3.png'
 
-Our [Incident Intelligence](/docs/new-relic-one/use-new-relic-one/new-relic-ai/get-started-incident-intelligence) uses logic to correlate your [incidents](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence#issue-feed). We call these logic "decisions." We have built-in decisions and you can create and customize your own on the Incident Intelligence **Decisions** UI page. The more optimally you configure decisions, the better we will group and correlate your incident events, resulting in reduced noise and increased context for on-call teams.
+Our [incident intelligence](/docs/new-relic-one/use-new-relic-one/new-relic-ai/get-started-incident-intelligence) uses logic to correlate your [incidents](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence#issue-feed). We call these logic "decisions." We have built-in decisions and you can create and customize your own on the incident intelligence **Decisions** UI page. The more optimally you configure decisions, the better we will group and correlate your incident events, resulting in reduced noise and increased context for on-call teams.
 
 <img
   title="NRAI_Decisions_Index.png"
   alt="Our AI correlates data related to incidents in the Decisions UI."
   src={nraiDecisionsIndex}
 />
 
-**[one.newrelic.com](https://one.newrelic.com) > Applied Intelligence > Incident intelligence > Decisions**: Our UI shows how each decision correlates incidents.
+**[one.newrelic.com](https://one.newrelic.com) > Applied intelligence > Incident intelligence > Decisions**: Our UI shows how each decision correlates incidents.
 
 ## Key concepts
 
 Here are some key concepts for understanding our decisions logic:
 
-* **What is "correlation" and how does it work?** For the [incident events](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence#issue-feed) being sent into Incident Intelligence from your various alerting engines, the most recently created and active incidents are available for correlation. Correlation occurs between two events whenever the criteria in any decision is met. All the events available for correlation are tested against each other in all possible pair combinations and a "greedy merge" is performed. This means that if incident A correlates with B into an [issue](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence#issue-feed) and incident B correlates with incident C into another issue, then AB and BC will also merge together resulting in a single issue including A, B, and C.
+* **What is "correlation" and how does it work?** For the [incident events](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence#issue-feed) being sent into incident intelligence from your various alerting engines, the most recently created and active incidents are available for correlation. Correlation occurs between two events whenever the criteria in any decision is met. All the events available for correlation are tested against each other in all possible pair combinations and a "greedy merge" is performed. This means that if incident A correlates with B into an [issue](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence#issue-feed) and incident B correlates with incident C into another issue, then AB and BC will also merge together resulting in a single issue including A, B, and C.
 * **What types of logic can be used in a decision?** At a high level, decisions allow you to define logic based on time (duration between events), frequency (number of events), context (metadata structure & values), and [topology](#topology) (entity relationships).
 
 ## Review your active decisions [#decisions]
 
-Decisions determine how Incident Intelligence correlates incidents together. By default, a broad set of global decisions is enabled when you start using Incident Intelligence.
+Decisions determine how incident intelligence correlates incidents together. By default, a broad set of global decisions is enabled when you start using incident intelligence.
 
 To review existing decisions:
 
-1. Go to **[one.newrelic.com](https://one.newrelic.com)** and click **Alerts & AI**. In the left navigation, under **Incident Intelligence**, click **Decisions**.
+1. Go to **[one.newrelic.com](https://one.newrelic.com)** and click **Alerts & AI**. In the left navigation, under **Incident intelligence**, click **Decisions**.
 2. Review the list of active decisions. To see the rule logic that creates correlations between your issues, click the decision.
 3. To see examples of incidents the decision correlated, click the **Recent correlations** tab.
 4. Use any of the other options to enable or disable these global decisions.
@@ -63,7 +63,7 @@ From the UI, you can view the [underlying NRQL queries](/docs/query-your-data/nr
   src={iiDecisionsStatistics}
 />
 
-**[one.newrelic.com](https://one.newrelic.com) > Applied Intelligence > Incident intelligence > Decisions**: Some example statistics from the decisions UI.
+**[one.newrelic.com](https://one.newrelic.com) > Applied intelligence > Incident intelligence > Decisions**: Some example statistics from the decisions UI.
 
 Some definitions of statistics:
 
@@ -87,15 +87,15 @@ To get started, click on a suggested decision, located under the statistics bloc
   src={screenShot20200727At65041Am}
 />
 
-**[one.newrelic.com](https://one.newrelic.com) > Applied Intelligence > Incident intelligence > Decisions**: Suggested decision block
+**[one.newrelic.com](https://one.newrelic.com) > Applied intelligence > Incident intelligence > Decisions**: Suggested decision block
 
 If there isn't enough data to see the correlation rate, a link right below the percentage estimate will guide you to other sources you can add to get stronger results. **Note: if you have less than 5000 incidents per month, you probably won't have suggested decisions.**
 
 To add the suggested decision, click **Activate decision** and it will appear enabled, alongside the other decisions. If the decision isn't relevant to your needs, click **Dismiss**.
 
 ## Create custom decisions [#customize]
 
-You can reduce noise and improve correlation by building your own custom decisions. To start building a decision, go to **[one.newrelic.com](https://one.newrelic.com)** and click **Alerts & AI**. In the left navigation, under **Incident Intelligence**, click **Decisions**, then click **Add a decision**. Tips on how to use that UI are in the table below.
+You can reduce noise and improve correlation by building your own custom decisions. To start building a decision, go to **[one.newrelic.com](https://one.newrelic.com)** and click **Alerts & AI**. In the left navigation, under **Incident intelligence**, click **Decisions**, then click **Add a decision**. Tips on how to use that UI are in the table below.
 
 When building a decision, steps 1, 2 and 3 are optional on their own but at least one must be defined in order to create a decision.
 
@@ -212,7 +212,7 @@ Here are technical details on the similarity algorithms we use:
           <td>
             The Levenshtein distance between two strings is the minimum number of single-character edits to get from one string to the other. Allowed edit operations are deletion, insertion, and substitution.
 
-            The default similarity threshold for Applied Intelligence decisions is an edit distance of 3. You can change this in the **Advanced mode** of the decision builder.
+            The default similarity threshold for applied intelligence decisions is an edit distance of 3. You can change this in the **Advanced mode** of the decision builder.
           </td>
         </tr>
 
@@ -885,7 +885,7 @@ Run the simulation with different attributes as many times as you need until you
 
 ## Topology correlation [#topology]
 
-What do we mean by “topology”? For New Relic's Applied Intelligence, topology is a representation of your service map: how the services and resources in your infrastructure relate to one another.
+What do we mean by “topology”? For New Relic's applied intelligence, topology is a representation of your service map: how the services and resources in your infrastructure relate to one another.
 
 When you [create a custom decision](#build-decision), you can use our topology correlation, which finds relationships between incident sources to determine if [incidents](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence#issue-feed) should correlate. Topology correlation is designed to improve the quality of your correlations and the speed at which they're found.
 
@@ -951,7 +951,7 @@ To set up your topology, you'll use [our NerdGraph API](#create-topology-graph).
 
 ### Add attributes to incident events [#add-attributes]
 
-Incidents are connected to vertices using a vertex's defining attributes (in the example topology under [Topology explained](#topology-explained), each vertex has a defining attribute "CID" with a unique value). Next, Applied Intelligence finds a vertex that matches the attribute.
+Incidents are connected to vertices using a vertex's defining attributes (in the example topology under [Topology explained](#topology-explained), each vertex has a defining attribute "CID" with a unique value). Next, applied intelligence finds a vertex that matches the attribute.
 
 If the defining attribute you'd like to use on your vertices isn't already on your incident events there are a few ways to add it:
 

src/content/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/eu-us-datacenters-incident-intelligence.mdx

@@ -1,14 +1,14 @@
 ---
-title: EU/US datacenters and Incident Intelligence
+title: EU/US datacenters and incident intelligence
 tags:
   - Alerts and applied intelligence
   - Applied intelligence
   - Incident intelligence
-metaDescription: 'Read about how to our EU and US datacenters work with Incident Intelligence.'
+metaDescription: 'Read about how to our EU and US datacenters work with incident intelligence.'
 redirects:
   - /docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence/#datacenter
 ---
 
-New Relic's Incident Intelligence service is performed solely in the United States. By using New Relic Incident Intelligence, you agree that New Relic may move your data to, and process your data in, the US region. This applies whether you store your data in New Relic's US region data center or in our [EU region data center](/docs/using-new-relic/welcome-new-relic/get-started/introduction-eu-region-data-center).
+New Relic's incident intelligence service is performed solely in the United States. By using New Relic incident intelligence, you agree that New Relic may move your data to, and process your data in, the US region. This applies whether you store your data in New Relic's US region data center or in our [EU region data center](/docs/using-new-relic/welcome-new-relic/get-started/introduction-eu-region-data-center).
 
 If you elect to use the Suggested Responder feature and manage EU-based individuals, you may need to confirm that an appropriate data processing agreement is in place.