@@ -15,7 +15,7 @@ You can find your [AWS Access Keys](https://console.aws.amazon.com/iam/home?#sec
15
15
16
16
{% include deploy/providers/s3.md content=content %}
17
17
18
- ## Setting an ACL
18
+ ## Set an ACL
19
19
20
20
You can set the acl of your uploaded files via the ` acl ` option like this:
21
21
@@ -123,7 +123,7 @@ deploy:
123
123
` ` `
124
124
{: data-file=".travis.yml"}
125
125
126
- # # Deploy to Multiple Buckets:
126
+ # # Deploy to Multiple Buckets
127
127
128
128
If you want to upload to multiple buckets, use multiple deployment configurations :
129
129
@@ -145,7 +145,7 @@ deploy:
145
145
You can deploy only when certain conditions are met.
146
146
See [Conditional Releases with `on:`](/user/deployment/#conditional-releases-with-on).
147
147
148
- # # Setting the content encoding
148
+ # # Set the content encoding
149
149
150
150
S3 uploads can optionally set the HTTP header `Content-Encoding`. This header
151
151
allows files to be sent compressed while retaining file extensions and the
@@ -164,7 +164,7 @@ deploy:
164
164
If the file is compressed with `gzip` or `compress`, it will be uploaded with
165
165
the appropriate header.
166
166
167
- # # Setting the charset on the content- type
167
+ # # Set the charset on the content type
168
168
169
169
S3 can take a content-type header. Normally this doesn't include a character
170
170
set as well. If you would like to add a character set, add the
@@ -246,9 +246,9 @@ deploy:
246
246
{: data-file=".travis.yml"}
247
247
248
248
249
- # # Using S3-compatible Object Storage
249
+ # # Use S3-compatible Object Storage
250
250
251
- You can use an S3-compatible object storage such as Digital Ocean Spaces
251
+ You can use S3-compatible object storage such as Digital Ocean Spaces
252
252
by setting the `endpoint` key.
253
253
254
254
` ` ` yaml
0 commit comments