fix(Alerts): Added Sammie's comments

src/content/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents.mdx

@@ -29,14 +29,53 @@ import alertsBySignal from 'images/alerts_diagram_by-signal.webp'
   In this document, we use the new terms "issue" and "incident." Please see [this article](https://discuss.newrelic.com/t/new-terminology-coming-for-alerts/163727) for a full explanation of these terms.
 </Callout>
 
-An issue is a collection of one or more incidents.
+To make the most of the info on this page, we recommend understanding the meaning of these terms:
 
-Issues determine when you're notified about incidents disrupting your business. These incidents occur when your given alert conditions (like CPU overage, synthetic monitoring crashes, or slow web app response times) are met.
+* **Issues**. Issues are groups of incidents related to the same underlying problem. When a new incident is created, incident intelligence opens an issue and evaluates other open issues for possible correlation. See [Issues and incident management and response](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/Issues-and-Incident-management-and-response/) for more information.
+
+* **Incidents**. Incidents are groups of events that describe the symptoms affecting your system over time. See [View violation and event details for incidents](/docs/alerts-applied-intelligence/new-relic-alerts/alert-incidents/view-violation-event-details-incidents/) for more information.
+
+* **Conditions**. A condition describes a monitored data source and the behavior of that data source that will be considered an incident. See [Create conditions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/) for more information.
+
+* **Policies**. A policy is a group of one or more conditions. See [Manage your policies](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) for more information.
+
+Issues determine when you're notified about incidents disrupting your business. These incidents occur when they meet your alert conditions. For example, you can have alert conditions about CPU overage, synthetic monitoring crashes, or slow web app response times.
 
 When you can control the policy conditions that create issues, you make sure that you're notified about important ongoing or recurring problems. This way you won't be bombarded with unnecessary notifications and avoid noise.
 
 Learn how to set issue preferences by your policy, condition, or condition and signal combination.
 
+## Select your issue preference [#preference-procedures]
+
+By default, a single issue record is created for each policy.
+
+To change the issue preference for the selected policy:
+
+1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (policies)**.
+2. Select a policy.
+
+<img
+  title="A screenshot showing where the issue preference button is inside the alerts user interface."
+  alt="A screenshot showing where the issue preference button is inside the alerts user interface."
+  src={alertsIncidentPreferenceUi}
+/>
+
+<figcaption>
+  Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (policies) > (select a policy)**. The selected policy page shows how alerts rolls up issues for alert notifications and UI details. The default option is **One issue per policy**. To choose a different option for this policy, click **Issue creation preference**.
+</figcaption>
+
+3. Click **Issue creation preference**, select your choice of available [options](#preference-options), and then **Save**.
+
+<img
+  width="60%;"
+  class="center"
+  title="A screenshot showing how to change your issue preferences on the alerts user interface."
+  alt="A screenshot showing how to change your issue preferences on the alerts user interface."
+  src={alertsIncidentPreferenceOptions}
+/>
+
+Repeat these steps for each policy as needed.
+
 ## Critical and warning incidents [#incident-types]
 
 Choose from two threshold types when a policy condition is met:
@@ -117,35 +156,6 @@ Each issue preference option has its own advantages. You can select any preferen
   </tbody>
 </table>
 
-## Select your issue preference [#preference-procedures]
-
-By default, a single issue record is created for each policy.
-
-To change the issue preference for the selected policy:
-
-1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (policies)**, and then **select a policy**.
-2. Click **Issue creation preference**, select your choice of available [options](#preference-options), and then **Save**.
-
-Repeat these steps for each policy as needed.
-
-<img
-  title="A screenshot showing where the issue preference button is inside the alerts user interface."
-  alt="A screenshot showing where the issue preference button is inside the alerts user interface."
-  src={alertsIncidentPreferenceUi}
-/>
-
-<img
-  width="60%;"
-  class="center"
-  title="A screenshot showing how to change your issue preferences on the alerts user interface."
-  alt="A screenshot showing how to change your issue preferences on the alerts user interface."
-  src={alertsIncidentPreferenceOptions}
-/>
-
-<figcaption>
-  Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (policies) > (select a policy)**. The selected policy page shows how alerts rolls up issues for alert notifications and UI details. The default option is **One issue per policy**. To choose a different option for this policy, click **Issue creation preference**.
-</figcaption>
-
 ## One issue per policy (default) [#preference-policy]
 
 Choose the **One issue per policy** preference if your policy and its conditions have a focused scope, like monitoring one entity.