From 585e1d40749528bc69ffea385d2b6b21bac50ae4 Mon Sep 17 00:00:00 2001
From: Baptiste Arnaud <contact@baptiste-arnaud.fr>
Date: Wed, 1 Nov 2023 13:51:38 +0100
Subject: [PATCH] :pencil2: Fix CORSRules content typo for S3 config

---
 apps/docs/docs/self-hosting/guides/s3.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/apps/docs/docs/self-hosting/guides/s3.md b/apps/docs/docs/self-hosting/guides/s3.md
index 11c6dbdee..cfc39459f 100644
--- a/apps/docs/docs/self-hosting/guides/s3.md
+++ b/apps/docs/docs/self-hosting/guides/s3.md
@@ -21,16 +21,16 @@ To function properly, your S3 bucket must have the following configuration:
   {
     "CORSRules": [
       {
-        "AllowedOrigins": ["*"],
-        "AllowedMethods": ["GET"],
         "AllowedHeaders": ["*"],
-        "MaxAgeSeconds": 3000
+        "AllowedMethods": ["PUT", "POST"],
+        "AllowedOrigins": ["*"],
+        "ExposeHeaders": ["ETag"]
       }
     ]
   }
   ```
 
-- Access policy:
+- Access policy (replace `<bucket-name>` with the name of your S3 bucket):
   ```json
   {
     "Version": "2012-10-17",
@@ -60,10 +60,10 @@ Some S3 providers like AWS provide a user interface that allows you to directly
    {
      "CORSRules": [
        {
-         "AllowedOrigins": ["*"],
-         "AllowedMethods": ["GET"],
          "AllowedHeaders": ["*"],
-         "MaxAgeSeconds": 3000
+         "AllowedMethods": ["PUT", "POST"],
+         "AllowedOrigins": ["*"],
+         "ExposeHeaders": ["ETag"]
        }
      ]
    }