Merge pull request #2379 from pauljewellmsft/known-issues

Update known issues to account for latest GA version

Author: pauljewellmsft

api/overview/azure/latest/storage.md

@@ -1,14 +1,14 @@
----
-title: Azure Storage SDK for .NET
-description: Reference for Azure Storage SDK for .NET
-author: seanmcc-msft
-ms.author: seanmcc
-ms.data: 09/12/2023
-ms.topic: reference
-ms.devlang: dotnet
-ms.service: storage
-ms.date: 09/19/2022
----
+---
+title: Azure Storage SDK for .NET
+description: Reference for Azure Storage SDK for .NET
+author: seanmcc-msft
+ms.author: seanmcc
+ms.data: 09/12/2023
+ms.topic: reference
+ms.devlang: dotnet
+ms.service: storage
+ms.date: 09/19/2022
+---
 # Azure Storage client libraries for .NET
 
 The Azure Storage client libraries for .NET offer a convenient interface for making calls to Azure Storage. For more information about Azure Storage, see [Introduction to Azure Storage](/azure/storage/common/storage-introduction).
@@ -75,7 +75,7 @@ This section details known issues for the Azure Storage client libraries for .NE
 
 ### InvalidHeaderValue error message when using beta version of SDK
 
-In rare scenarios, applications that have upgraded to a beta version of the SDK can receive an `InvalidHeaderValue` error message. This issue can occur when using any of the Storage libraries. The error message looks similar to the following sample:
+In rare scenarios, applications that have upgraded to the latest beta or generally available version of the SDK can receive an `InvalidHeaderValue` error message. This issue can occur when using any of the Storage libraries. The error message looks similar to the following sample:
 
 ```console
 HTTP/1.1 400 The value for one of the HTTP headers is not in the correct format.
@@ -90,4 +90,4 @@ RequestId:<REMOVED>
 Time:2023-05-19T17:10:34.2972651Z</Message><HeaderName>x-ms-version</HeaderName><HeaderValue>yyyy-mm-dd</HeaderValue></Error> 
 ```
 
-If you've upgraded to a beta version of the SDK and you experience this error, it's recommended that you downgrade to a supported, generally available version of the SDK to see if the issue resolves. If the issue persists, or if the recommendation is not feasible, [open a support ticket](https://ms.portal.azure.com/#create/Microsoft.Support) to explore further options.
+If you've upgraded to the latest beta or generally available version of the SDK and you experience this error, it's recommended that you downgrade to the previous generally available version of the SDK to see if the issue resolves. If the issue persists, or if the recommendation is not feasible, [open a support ticket](https://ms.portal.azure.com/#create/Microsoft.Support) to explore further options.