Some updates

Author: normesta

articles/storage/common/storage-ref-azcopy-error-codes.md

@@ -25,4 +25,4 @@ The following errors can be returned by the Azure Blob Storage API when working
 | Not Found (404) | ResourceNotFound | The specified resource doesn't exist. |
 | Conflict (409) | ResourceTypeMismatch | The specified resource type doesn't match the type of the existing resource. |
 | Internal Server Error (500) | CannotVerifyCopySource | This error is returned when you try to copy a blob from a source that is not accessible. More information and possible workarounds can be found [here](/troubleshoot/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction#copy-blobs-between-storage-accounts-in-a-hub-spoke-architecture-using-private-endpoints). |
-| Service Unavailable (503) | ServerBusy | Messages:<br><br>The server is currently unable to receive requests. Please retry your request.<br><br>Ingress is over the account limit.<br><br>Egress is over the account limit.<br><br>Operations per second is over the account limit.<br><br>You can use the Storage insights to monitor the account limits. See [Monitoring your storage service with Azure Monitor Storage insights](storage-insights-overview.md). |
+| Service Unavailable (503) | ServerBusy | Error messages:<li>The server is currently unable to receive requests. Please retry your request.<li>Ingress is over the account limit.<li>Egress is over the account limit.<li>Operations per second is over the account limit.<li>You can use the Storage insights to monitor the account limits. See [Monitoring your storage service with Azure Monitor Storage insights](storage-insights-overview.md). |