Updates breaking change sections

Updates breaking change sections

release_notes/Service_Fabric_ReleaseNotes_70.md

@@ -35,12 +35,12 @@ Microsoft Azure Service Fabric 7.0 Release Notes
 - **Service Fabric Explorer**:  Added support for [managing Backup Restore service](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-backuprestoreservice-quickstart-azurecluster#using-service-fabric-explorer). This makes the following activities possible directly from within SFX: discovering backup and restore service, ability to create backup policies, enabling automatic backup for application, service, partitions,taking adhoc backup, triggering a restore operation apart from browsing existing backups.
 - **Additional cluster safety checks**: In this release we introduced a configurable seed node quorum safety check. This allows you to customize how many seed nodes must be available during cluster lifecycle and management scenarios. Operations which would take the cluster below the configured value are blocked. Today the default value is always a quorum of the seed nodes, for example, if you have 7 seed nodes, an operation that would take you below 5 seed nodes would be blocked by default. With this change, you could make the minimum safe value 6, which would allow only one seed node to be down at a time.   
 
-## Upcoming Breaking Changes
+## Current And Upcoming Breaking Changes
 - For customers [using service fabric to export certificates into their linux containers](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-securing-containers), the export mechanism will be changed in an upcoming CU to encrypt the private key included in the .pem file, with the password being stored in an adjacent .key file.
-- For customers using service fabric managed identities, **please switch to new environment variables ‘IDENTITY_ENDPOINT’ and ‘IDENTITY_HEADER’**. The prior environment variables    
+- Starting in Service Fabric 7.0 version, customers using service fabric managed identities, **please switch to new environment variables ‘IDENTITY_ENDPOINT’ and ‘IDENTITY_HEADER’**. The prior environment variables    
   'MSI_ENDPOINT', ‘MSI_ENDPOINT_’ and 'MSI_SECRET' are now deprecated and will be removed in next CU release.
-- We have changed the default value for the PreferUpgradedUDs config in the [PlacementAndLoadBalancing section of the ClusterManifest](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-fabric-settings#placementandloadbalancing).Based on numerous cases and customer issues, this default behavior should allow clusters to remain more balanced during upgrades. If you want to preserve today’s behavior for your workload, please perform a cluster configuration upgrade to explicitly set the value to true either prior to or as a part of upgrading your cluster to 7.0.
-- We have fixed a calculation bug in the Cluster Resource Manager which impacts how node resource capacities are calculated in cases where a user manually provides the values for node resource capacities. The impact of this fix is that the Cluster Resource Manager will now consider there to be less usable capacity in the cluster. More details in the [Resource governance documentation page](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-resource-governance).
+- Starting in Service Fabric 7.0 version, we have changed the default value for the PreferUpgradedUDs config in the [PlacementAndLoadBalancing section of the ClusterManifest](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-fabric-settings#placementandloadbalancing).Based on numerous cases and customer issues, this default behavior should allow clusters to remain more balanced during upgrades. If you want to preserve today’s behavior for your workload, please perform a cluster configuration upgrade to explicitly set the value to true either prior to or as a part of upgrading your cluster to 7.0.
+- Starting in Service Fabric 7.0 version, we have fixed a calculation bug in the Cluster Resource Manager which impacts how node resource capacities are calculated in cases where a user manually provides the values for node resource capacities. The impact of this fix is that the Cluster Resource Manager will now consider there to be less usable capacity in the cluster. More details in the [Resource governance documentation page](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-resource-governance).
 - We are planning to update the way Service Fabric performs equality comparison for Boolean values when evaluating placement constraints. Today Service Fabric uses case-sensitive comparison for Boolean values in this scenario. Starting in one of the subsequent releases, we will be changing this comparison to be case-insensitive (which is a common practice in the software industry).
 - For customers using [Windows Azure Diagnostics](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-diagnostics-event-aggregation-wad) to collect Reliable Collections events, the Reliable Collections ETW manifest provider has been changed to *02d06793-efeb-48c8-8f7f-09713309a810*, and should be accounted for in the WAD config.
 - Currently Service Fabric ships the following nuget packages as a part of our    ASP.Net Integration and support: