links updated for docs

release_notes/Service-Fabric-70CU2-releasenotes.md

@@ -34,7 +34,7 @@ Microsoft Azure Service Fabric 7.0 Second Refresh Release Notes
 | **Windows 7.0.464.9590  <br>  Ubuntu 7.0.464.1**  | **Bug** | update application failed with error FABRIC_E_APPLICATION_UPDATE_IN_PROGRESS | **Impact**:  There is a racing problem when ClusterManager fails over during updating app. After ClusterManager is recovered, the pending updating is not picked up by ClusterManager and remains in inprogress status forever, so new update request cannot be accepted. On the other hand, delete app request doesn't clean up update information in ClusterManager, so even if the app is recreated after deleted, it will still show update in progress. <br>**Fix**:  1) Clean up update information in ClusterManager when deleting application, in case there is update in progress that prevents new update app request even when app is recreated after deleted. 2) Recover pending app update context when ClusterManager is recovered. <br> **Workaround**: N/A |
 | **Windows 7.0.464.9590  <br>  Ubuntu 7.0.464.1**  | **Bug** | Cluster configuration change may not be notified to Fabric Client. | **Impact**:  Cluster configuration change is notified to configuration change handlers that a service registers to read new configuration values at change. A race condition is found at delivering notification to Fabric client user. For example, the certificate change in Cluster Manifest may not be notified to ImageStoreService and the configuration upgrade could fail by the race condition. <br>**Fix**: The race condition is fixed. <br> **Workaround**: Restart the impacted replica |
 | **Windows 7.0.464.9590  <br>  Ubuntu 7.0.464.1**  | **Feature** | ImageStoreService uses custom connection to exchange files. | **Brief desc**:  ImageStoreService uses custom connection in various paths of file exchange. The file delivery includes uploading packages to Service Fabric cluster, downloading package to a node at replica instantiation, and replicating files between ImageStoreService replica. |
-| **Windows 7.0.464.9590  <br>  Ubuntu 7.0.464.1**  | **Feature** | PreviewFeature: Drain requests before closing stateless instances. | **Brief desc**:  For planned stateless instance downtime,  when the application/cluster is upgraded or nodes are getting deactivated, there are a few connections drops which are observed because the endpoint exposed by the instances is removed after it goes down. To avoid getting connections drops for planned downtime, configure the replica close delay duration in the service configuration. [**Documentation**](https://docs.microsoft.com/azure/service-fabric/service-fabric-application-upgrade-advanced#avoid-connection-drops-during-planned-downtime-of-stateless-services)|
+| **Windows 7.0.464.9590  <br>  Ubuntu 7.0.464.1**  | **Feature** | PreviewFeature: Drain requests before closing stateless instances | **Brief desc**:  For planned stateless instance downtime,  when the application/cluster is upgraded or nodes are getting deactivated, there are a few connections drops which are observed because the endpoint exposed by the instances is removed after it goes down. To avoid getting connections drops for planned downtime, configure the replica close delay duration in the service configuration.[**Documentation**](https://docs.microsoft.com/azure/service-fabric/service-fabric-application-upgrade-advanced#avoid-connection-drops-during-planned-downtime-of-stateless-services)|
 | **Windows 7.0.464.9590  <br>  Ubuntu 7.0.464.1**  | **Bug** | FabricBRSSetup.exe crashes during cluster upgrade. | **Impact**:  Cluster upgrade can sometimes fail with FabricBRSSetup.exe crashing due to a failure to ACL listener ports, when hosting didn't properly cleanup the same port when it was closing the previous time. Fix has been done to properly cleanup such a port ACLing. <br> **Workaround**: Remove FabricBRS and then upgrade SF cluster. |
 | **Windows 7.0.464.9590  <br>  Ubuntu 7.0.464.1**  | **Bug** | Fabric.exe crashes occasionally during initial health reporting. | **Impact**:  Fabric.exe may crash due to a race condition around when it's first brought up. This condition only occurs during the first system health report sent. If the first report is successful, issue will not reoccur for the remainder of the process. <br> **Workaround**: Self healing. Fabric.exe will come back if it crashes and issue will not be hit again until process restart. |
 | **Windows 7.0.464.9590  <br>  Ubuntu 7.0.464.1**  | **Bug** | Cluster health string gives incorrect application and node counts. | **Impact**:  The ClusterHealth ToString method of System.Fabric.dll gives swapped node and application counts. This issue is not reflected in SFX, but can be seen in PowerShell's Get-ServiceFabricClusterHealth API if the returned result is stored and ToString is called, for example. The incorrect string has format "ClusterHealth: {0}, {1} nodes, {2} applications, {3} events". <br> **Workaround**: Swap the node and application counts. |