Update release-notes.md

Author: atinb

articles/energy-data-services/release-notes.md

@@ -13,7 +13,7 @@ ms.custom: template-concept #Required; leave this attribute/value as-is.
 
 [!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
 
-Microsoft Energy Data Services receives improvements on an ongoing basis. To stay up to date with the most recent developments, this article provides you with information about:
+Microsoft Energy Data Services is updateed on an ongoing basis. To stay up to date with the most recent developments, this article provides you with information about:
 
 - The latest releases
 - Known issues
@@ -26,41 +26,34 @@ Microsoft Energy Data Services receives improvements on an ongoing basis. To sta
 
 ### Key Announcement
 
-Microsoft Energy Data Services is now available as a public preview. 
+Microsoft Energy Data Services is now available in public preview. 
 
-Microsoft Energy Data Services conforms with the requirements of the Release-3, [Milestone-12](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/M12-Release-Notes) of OSDU™ Technical Standard, Version 1.0.
+Microsoft Energy Data Services is developed in alignment with the emerging requirements of the OSDU™ Technical Standard, Version 1.0. and is currently aligned with Mercury Release(R3), [Milestone-12](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/M12-Release-Notes).
 
 ### Partition & User Management
 
-- You can create [new data partitions](how-to-add-more-data-partitions.md) (up to five) in your existing Microsoft Energy Data Services instance. Earlier, you could create a data partition only while provisioning the instance.
-- The domain name for your entitlement groups for [user management](how-to-manage-users.md) is changed to "dataservices.energy".
+- New data partitions can be [created dynamically](how-to-add-more-data-partitions.md) as needed post provising of the platform (up to five). Earlier, data partitions could only be created when provisioning a new instance.
+- The domain name for entitlement groups for [user management](how-to-manage-users.md) has been changed to "dataservices.energy".
 
 ### Data Ingestion
 
-- Microsoft Energy Data Services - Enabled support for user context in ingestion ([ADR: Issue 52](https://community.opengroup.org/osdu/platform/data-flow/ingestion/home/-/issues/52)) (not yet supported in the Azure OSDU™ community edition)
-  - In Microsoft Energy Data Services, the User identity is preserved and passed on to all ingestion workflow related services using the newly introduced _x-on-behalf-of_ header.
-  - In Azure OSDU™ community edition, by using elevated SPN permissions, users could call the workflow service and trigger an ingestion job even without appropriate service level entitlements on the underlying dependent services. In Microsoft Energy Data Services, a user needs to have appropriate service level entitlements on all dependent services involved in the ingestion workflow
-  - In Azure OSDU™ community edition, users who weren't part of the same data entitlement group could accidentally modify and corrupt data (using elevated SPN permissions). In Microsoft Energy Data Services, only users belonging to the same data entitlement group can modify data, and the modified user and date information are captured.
+- Microsoft Energy Data Services - Enabled support for user context in ingestion ([ADR: Issue 52](https://community.opengroup.org/osdu/platform/data-flow/ingestion/home/-/issues/52)) 
+  - User identity is preserved and passed on to all ingestion workflow related services using the newly introduced _x-on-behalf-of_ header. A user needs to have appropriate service level entitlements on all dependent services involved in the ingestion workflow
 - Workflow service payload is restricted to a maximum of 2 MB. If it exceeds, the service will throw an HTTP 413 error. This restriction is placed to prevent workflow requests from overwhelming the server.
 - Microsoft Energy Data Services uses Azure Data Factory (ADF) to run large scale ingestion workloads.
 
 ### Search
 
-- Improved security as Elasticsearch images is now pulled from Microsoft's internal Azure Container Registry instead of public repositories.
+- Improved security as Elasticsearch images are now pulled from Microsoft's internal Azure Container Registry instead of public repositories.
 - Improved security by enabling encryption in transit for Elasticsearch, Registration, and Notification services.
 
 ### Monitoring
 
-- You can create diagnostic settings to export [Airflow](how-to-integrate-airflow-logs-with-azure-monitor.md) and [Elasticsearch](how-to-integrate-elastic-logs-with-azure-monitor.md) logs from your Microsoft Energy Data Services instance to Azure Monitor.
-
-### Hardware & Software
-
-- Your Microsoft Energy Data Services instance runs on the latest version of Azure Kubernetes Services (AKS) clusters – [version 1.24.](https://kubernetes.io/blog/2022/04/07/upcoming-changes-in-kubernetes-1-24/)
+- Diagnostic settings can be exported from [Airflow](how-to-integrate-airflow-logs-with-azure-monitor.md) and [Elasticsearch](how-to-integrate-elastic-logs-with-azure-monitor.md) to Azure Monitor.
 
 ### Region Availability
 
-- In Preview, Availability Zones will be available by default in select regions. All new Microsoft Energy Data Services instances created in these select zones will have Availability Zones redundancy enabled on them upon creation.
-- The selected regions where Availability Zones will be offered on Microsoft Energy Data Services Preview are - South Central US, East US, West Europe, and North Europe.
+- Currently, Microsoft Energy Data Services is being offered in the following regions - South Central US, East US, West Europe, and North Europe.
 
 ---