Merge pull request #2712 from replicatedhq/registry-2gb-limitation

Reposition the 2gb layer from a known issue to a limitation

Author: AmberAlston

docs/vendor/private-images-replicated.mdx

@@ -24,9 +24,7 @@ The Replicated registry has the following limitations:
 
 * When using Docker Build to build and push images to the Replicated registry, provenance attestations are not supported. To avoid a 400 error, include the `--provenance=false` flag to disable all provenance attestations. For more information, see [docker buildx build](https://docs.docker.com/engine/reference/commandline/buildx_build/#provenance) and [Provenance Attestations](https://docs.docker.com/build/attestations/slsa-provenance/) in the Docker documentation.
 
-## Known Issue
-
-There is a known issue with the Replicated registry that can cause a timeout error when attempting to push images with layers close to 2GB. This results in an error message similar to the following: `received unexpected HTTP status: 524`. If you see a 524 error, build your image with smaller image layers and then push the image again. If you continue seeing a 524 error, reduce the size of the image layers again.
+* You might encounter a timeout error when pushing images with layers close to or exceeding 2GB in size, such as: "received unexpected HTTP status: 524." To work around this, reduce the size of the image layers and push the image again. If the 524 error persists, continue decreasing the layer sizes until the push is successful.
 
 ## Push Images to the Replicated Registry
 
@@ -78,4 +76,4 @@ Docker format:
    docker push registry.replicated.com/myapp/worker:1.0.1
    ```    
 
-1. In the [Vendor Portal](https://vendor.replicated.com/), go to **Images** and scroll down to the **Replicated Private Registry** section to confirm that the image was pushed. 
+1. In the [Vendor Portal](https://vendor.replicated.com/), go to **Images** and scroll down to the **Replicated Private Registry** section to confirm that the image was pushed.