Update: 25-04-2025

cldocid2 · cldocid2 · commit cbfb8d7c44f1 · 2025-04-25T05:08:15.000Z
diff --git a/en-create-topic.md b/en-create-topic.md
@@ -39,7 +39,7 @@ You can send notifications or alerts to multiple destination types, for example,
       - **Event type**: select event type from the list.
       - **Event subtype**: select event sub type from the event sub type list.
       - **Severity**: select severity from the severity list.
-      - **Advanced conditions**: create your own custom conditions, which must follow [JSONpath specifications](https://goessner.net/articles/JsonPath/). The correctly written rule will extract the appropriate data from the incoming request payload. {{site.data.keyword.en_short}} supports conditional operators `>=, <=, ==, >, <, !=, =~` and logical operators `||, &&` for JSONPath evaluation. You can validate your JSONPath [here](https://jsonpath.com/). If you want to add advanced conditions for event type, subtype, and severity, see the following [example](/docs/event-notifications?topic=event-notifications-en-create-en-topic#create-topic-example). Similarly you can add advanced conditions for the other available [payload fields](https://{DomainName}/apidocs/event-notifications#send-notifications-request/apidocs/event-notifications#send-notifications-request).
+      - **Advanced conditions**: create your own custom conditions, which must follow [JSONpath specifications](https://goessner.net/articles/JsonPath/). The correctly written rule will extract the appropriate data from the incoming request payload. {{site.data.keyword.en_short}} supports conditional operators `>=, <=, ==, >, <, !=, =~` and logical operators `||, &&` for JSONPath evaluation. You can validate your JSONPath [here](https://jsonpath.com/). If you want to add advanced conditions for event type, subtype, and severity, see the following [example](/docs/event-notifications?topic=event-notifications-en-create-en-topic#create-topic-example). Similarly you can add advanced conditions for the other available [payload fields](https://{DomainName}/apidocs/event-notifications#send-notifications-request).
 
       The "=~" operator is a powerful tool that helps you search for patterns in strings using regular expressions.
       {: note}
diff --git a/en-data-security.md b/en-data-security.md
@@ -56,12 +56,12 @@ If you no longer need an instance of {{site.data.keyword.en_short}}, you can del
 To restore a deleted instance or to delete the instance permanently, you can use Resource Reclamations. For more information about resource reclamation, see [Using Resource Reclamations](/docs/account?topic=account-resource-reclamation).
 
 ## Data security and compliance
-{: #en-data-security-and-compliance}
+{: #en-data-security-and-compliance1}
 
 {{site.data.keyword.en_short}} service has data security strategies in place to meet your compliance needs and ensure that your data remains secure and protected in the cloud.
 
 ### Security readiness
-{: #en-security-readiness}
+{: #en-security-readiness1}
 
 {{site.data.keyword.en_short}} ensures security readiness by adhering to {{site.data.keyword.IBM_notm}} best practices for systems, networking, and secure engineering.
 
@@ -71,7 +71,7 @@ To learn more about security controls across {{site.data.keyword.cloud_notm}}, s
 To learn more about how your data is secured in {{site.data.keyword.en_short}}, see [securing your data in {{site.data.keyword.en_short}}](/docs/event-notifications?topic=event-notifications-en-mng-data).
 
 #### Data encryption
-{: #en-data-encryption}
+{: #en-data-encryption1}
 
 {{site.data.keyword.en_short}} stores and encrypts details that are related to your destinations like email (sender, recipients, subject), or SMS (sender, recipient, details).
 
@@ -83,7 +83,7 @@ If you attempt to use a cipher that is not on this list, you may experience conn
 {: tip}
 
 ### Compliance readiness
-{: #en-compliance-readiness}
+{: #en-compliance-readiness1}
 
 {{site.data.keyword.en_short}} meets controls for global, industry, and regional compliance standards, including ISO
 27001/27017/27018/27701, and others.
@@ -92,6 +92,6 @@ For a complete listing of {{site.data.keyword.cloud_notm}} compliance certificat
 {: tip}
 
 #### ISO 27001, 27017, 27018, 27701
-{: #en-iso}
+{: #en-iso1}
 
 {{site.data.keyword.en_short}} is ISO 27001, 27017, 27018, and 27701 certified. You can view compliance certifications by visiting [Compliance on the {{site.data.keyword.cloud_notm}}](https://ibm.com/cloud/compliance){: external}.
diff --git a/en-destination-event-streams.md b/en-destination-event-streams.md
@@ -2,7 +2,7 @@
 
 copyright:
   years: 2025
-lastupdated: "2025-04-14"
+lastupdated: "2025-04-25"
 
 keywords: event-notifications, event notifications, about event notifications, destinations, Event Streams, event streams
 
@@ -78,7 +78,7 @@ To configure an {{site.data.keyword.messagehub}} destination, complete the follo
 Copy the **CRN**, that is used in the destination creation process. Use this copied CRN in the destination creation screen.
 
 #### Endpoint URL
-{: #en-endpoint-url}
+{: #en-event-streams-endpoint-url}
 
 Copy the **HTTP API endpoint** that needs to be used in the destination creation process. Use this copied endpoint in the destination creation screen.
 
diff --git a/en-managing-encryption.md b/en-managing-encryption.md
@@ -88,20 +88,20 @@ You are charged for your instance of {{site.data.keyword.en_short}} until you de
 {: important}
 
 ### Restoring access to data
-{: #restoring_access}
+{: #restoring-access}
 
 Access can be restored only if the key was not deleted. To restore access, re-enable your root key. After a short period of initialization, your {{site.data.keyword.en_short}} instance is restarted and starts accepting connections again. All data is retained, subject to the normal retention limits configured in your instance.
 
 A cloud logs event is generated to report the action. For more information, see [{{site.data.keyword.cloudaccesstrailshort}} events](/docs/event-notifications?topic=event-notifications-at_events).
 
 ### Rotating the key
-{: #rotating_key}
+{: #rotating-key}
 
 {{site.data.keyword.keymanagementserviceshort}} and {{site.data.keyword.hscrypto}} support the rotation of root keys, either on demand or on a schedule. When this occurs, {{site.data.keyword.en_short}} adopts the new key by rewrapping the DEK as described in [how customer-managed encryption works](#en-encryption-how).
 
 A cloud logs event is generated to report the action. For more information, see [{{site.data.keyword.cloudaccesstrailshort}} events](/docs/event-notifications?topic=event-notifications-at_events).
 
 ## Disabling customer-managed encryption
-{: #stop_customer_encryption}
+{: #stop-customer-encryption}
 
 After enabling customer-managed encryption, it is not possible to disable it. Instead, you must delete the service instance and create a new instance.
diff --git a/en-release-notes.md b/en-release-notes.md
@@ -2,7 +2,7 @@
 
 copyright:
   years: 2021, 2024
-lastupdated: "2025-04-24"
+lastupdated: "2025-04-25"
 
 keywords: event-notifications, event notifications, about event notifications
 
@@ -21,7 +21,7 @@ Looking for {{site.data.keyword.cloud_notm}} status, platform announcements, sec
 {: note}
 
 ## 15 April 2025
-{: #event-notifications-Oct2023}
+{: #event-notifications-April152025}
 {: release-note}
 
 {{site.data.keyword.cloud_notm}} {{site.data.keyword.en_short}} is now available in the Sao Paulo region
diff --git a/toc.yaml b/toc.yaml
@@ -75,7 +75,6 @@ toc:
           - en-destination-codeengine.md
           - en-destination-cloud-object-storage.md
           - en-destination-event-streams.md
-          - en-managing-encryption.md
           - en-test-destination.md
       - en-cfe-integrations.md
       - topicgroup:
