diff --git a/release_notes/Service-Fabric-70CU3-releasenotes.md b/release_notes/Service-Fabric-70CU3-releasenotes.md
index 26c9a59..0e8cf43 100644
--- a/release_notes/Service-Fabric-70CU3-releasenotes.md
+++ b/release_notes/Service-Fabric-70CU3-releasenotes.md
@@ -31,7 +31,6 @@ Microsoft Azure Service Fabric 7.0 Third Refresh Release Notes
| Versions | IssueType | Description | Resolution |
|----------|-----------|-|-|
-| **Windows 7.0.466.9590
Ubuntu 7.0.465.1** | **Bug** | Local user account name has prefix "WF-" | **Impact**: Service Fabric Runtime creates local user accounts for operations. Account names are generated from given inputs in Cluster Manifest. Some security monitoring tools raise an alarm when unknown local accounts are created. The account name didn't have a pattern and false alarms were raised.
**Fix**: Generated accounts have the known prefix.
**Workaround**: N/A |
| **Windows 7.0.466.9590
Ubuntu 7.0.465.1** | **Bug** | New config CompleteClientRequest in ClusterManager section | **Impact**: For create/delete app, ClusterManager completes client request until the create/delete operations are finished. If client request has a shorter timeout than ClusterManager, it's possible that client request is timed out but ClusterManager is not and keeps on creating/deleting apps until success.
**Fix**: Add a config CompleteClientRequest in ClusterManager section to allow completing client request when ClusterManager accepts request for create/delete app rather than holds the client request until operation is finished.
**Workaround**: N/A |
| **Windows 7.0.466.9590
Ubuntu 7.0.465.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.
**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.
**Workaround**: N/A |
| **Windows 7.0.466.9590
Ubuntu 7.0.465.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.
**Fix**: The race condition is fixed.
**Workaround**: Restart the impacted replica |