diff --git a/Getting-Started.md b/Getting-Started.md
index 1530eee..8cfc91c 100644
--- a/Getting-Started.md
+++ b/Getting-Started.md
@@ -175,14 +175,14 @@ docker build -f Dockerfile.local --no-cache -t localregistry/seaweedfs .
 You can use docker volumes to persist data:
 ```bash
 # start our weed server daemonized
-docker run --name weed -d -p 9333:9333 -p 8080:8080 -p 18080:8080 \
+docker run --name weed -d -p 9333:9333 -p 8080:8080 -p 18080:18080 \
   -v seaweedvolume:/data chrislusf/seaweedfs server -dir="/data"
 ```
 
 Alternatively, you can mount a directory on the host machine into the container:
 ```bash
 # start our weed server daemonized
-docker run --name weed -d -p 9333:9333 -p 8080:8080 -p 18080:8080 \
+docker run --name weed -d -p 9333:9333 -p 8080:8080 -p 18080:18080 \
   -v /opt/weedfs/data:/data chrislusf/seaweedfs server -dir="/data"
 ```
 Note that according to [Docker's documentation](https://docs.docker.com/storage/volumes/), volumes are the preferred mechanism for persisting data.
diff --git a/S3-Iceberg-Integration.md b/S3-Iceberg-Integration.md
index 523822a..35e1edd 100644
--- a/S3-Iceberg-Integration.md
+++ b/S3-Iceberg-Integration.md
@@ -73,6 +73,7 @@ s3.path-style-access=true
 s3.signer-type=AwsS3V4Signer
 s3.aws-access-key=YOUR_ACCESS_KEY
 s3.aws-secret-key=YOUR_SECRET_KEY
+s3.region=us-east-1
 ```
 
 ---