Removed references to features not yet released

Author: yelevin

defender-xdr/alerts-incidents-correlation.md

@@ -62,7 +62,7 @@ When two or more incidents are merged, a new incident is *not* created to absorb
 
 #### Merge direction
 
-The direction of the incident merge refers to which incident is the source and which is the target. This direction is determined by Microsoft Defender, based on its own internal logic, with the goal of maximizing information retention and access. The user doesn't have any input into this decision, even when merging incidents manually.
+The direction of the incident merge refers to which incident is the source and which is the target. This direction is determined by Microsoft Defender, based on its own internal logic, with the goal of maximizing information retention and access. The user doesn't have any input into this decision.
 
 #### Incident contents
 
@@ -73,7 +73,7 @@ The contents of the incidents are handled in the following ways:
 - A **`Redirected`** tag is added to the source incident.
 - Entities (assets etc.) follow the alerts they're linked to.
 - Analytics rules recorded as involved in the creation of the source incident are added to the rules recorded in the target incident.
-- Comments and activity log entries in the source incident are moved to the target incident.
+- Currently, comments and activity log entries in the source incident are *not* moved to the target incident.
 
 To see the source incident's comments and activity history, open the incident in Microsoft Sentinel in the Azure portal. The activity history includes the closing of the incident and the adding and removal of alerts, tags, and other items related to the incident merge. These activities are attributed to the identity *Microsoft Defender XDR - alert correlation*.