Fix typo and examples

Use bucket instead of container more consistently.

Client-compatibility-list.md

@@ -27,7 +27,7 @@ client.setS3ClientOptions(new S3ClientOptions().withPathStyleAccess(true));
 ```java
 sc.hadoopConfiguration.set("fs.s3a.impl", "org.apache.hadoop.fs.s3a.S3AFileSystem")
 sc.hadoopConfiguration.set("fs.s3a.endpoint", "127.0.0.1:4242")
-sc.hadoopConfiguration.set("fs.s3a.connection.ssl.enabled", "false") // if no SSL suppport
+sc.hadoopConfiguration.set("fs.s3a.connection.ssl.enabled", "false") // if no SSL support
 // if user/password access
 sc.hadoopConfiguration.set("fs.s3a.aws.credentials.provider", "org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider")
 sc.hadoopConfiguration.set("fs.s3a.access.key", "local-identity")
@@ -164,4 +164,4 @@ $ s3fs bucketname dirname \
       -o sigv2 \
       -o url=http://127.0.0.1:8080 \
       -o use_path_request_style
-```
+```

Middleware-alias-blobstore.md

@@ -1,8 +1,8 @@
-S3Proxy can use an alias for a backend container. This may be helpful to preserve bucket names when switching backends, for example. The alternate name can be specified as follows:
+S3Proxy can use an alias for a backend bucket. This may be helpful to preserve bucket names when switching backends, for example. The alternate name can be specified as follows:
 ```
 s3proxy.alias-blobstore.content=backend-data
 ```
 
 In the above example, requests for the bucket `content` are redirected to `backend-data`. This does not preclude using the name `backend-data`, however, when listing buckets `backend-data` bucket is replaced with `content` in the listing.
 
-S3Proxy does not allow mapping multiple aliases to the same backend bucket. Future work could expand this middleware to include a prefix, allowing a subset of a bucket to appear as a bucket to the S3Proxy clients.
+S3Proxy does not allow mapping multiple aliases to the same backend bucket. Future work could expand this middleware to include a prefix, allowing a subset of a bucket to appear as a bucket to the S3Proxy clients.

Middleware-bucket-locator.md

@@ -1,8 +1,8 @@
 s3proxy can be configured to select the backend by the bucket names. Each bucket
 for the backend must be specified in the properties file. Example:
 
-    s3proxy.bucket-locator.1=container1
-    s3proxy.bucket-locator.2=container2
+    s3proxy.bucket-locator.1=bucket1
+    s3proxy.bucket-locator.2=bucket2
 
 The indexing 1, 2, etc is only to differentiate the bucket entries. The `bucket-locator` middleware supports glob syntax for bucket names.
 

Middleware-regex.md

@@ -20,7 +20,7 @@ s3proxy.regex-blobstore.match.type_partition=^prefix/(\\w+)/(\\d{4})/(\\d{2})/(\
 s3proxy.regex-blobstore.replace.type_partition=prefix/date=$2-$3-$4/type=$1/$5
 ```
 
-will rewrite blob name from:
+will rewrite key name from:
 
 ```
 prefix/test/2023/01/01/test.txt

Middleware-storage-class-override.md

@@ -24,8 +24,8 @@ Then with this configuration you can run this test
 export AWS_ACCESS_KEY_ID=local-identity
 export AWS_SECRET_ACCESS_KEY=local-credential
 echo "put me in test" > test.txt
-aws s3 --endpoint-url http://127.0.0.1:8080 cp test.txt s3://mcourcy-testia/test.txt
-aws  s3api head-object --endpoint-url http://127.0.0.1:8080 --bucket mcourcy-testia --key test.txt
+aws s3 --endpoint-url http://127.0.0.1:8080 cp test.txt s3://BUCKETNAME/test.txt
+aws s3api head-object --endpoint-url http://127.0.0.1:8080 --bucket BUCKETNAME --key test.txt
 ```
 
 The output

Tips.md

@@ -18,10 +18,10 @@ s3proxy.authorization=none
 
 You can use `curl` to debug s3proxy when authentication is disabled (see above):
 
-* list containers in a storage account: `curl http://<proxy>/`
-* list blobs in a container: `curl http://<proxy>/<containername>`
-* add a new container: `curl -X PUT http://<proxy>/<newcontainername>`
-* add a new blob to a container: `curl -X PUT -T <filename> http://<proxy>/<containername>/<newblobname>`
+* list buckets in a storage account: `curl http://<proxy>/`
+* list blobs in a bucket: `curl http://<proxy>/<bucketname>`
+* add a new bucket: `curl -X PUT http://<proxy>/<newbucketname>`
+* add a new blob to a bucket: `curl -X PUT -T <filename> http://<proxy>/<bucketname>/<newblobname>`
 
 # Logging