Skip to content

Commit 4f31c41

Browse files
committed
Docs language cleanup
1 parent de605f3 commit 4f31c41

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

frontend/docs/docs/deploy/admin/org-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ The first step to configuring custom storage with an organization is to add the
1414
curl -X POST -H "Content-type: application/json" -H "Authorization: Bearer <jwt token>" https://app.browsertrix.com/api/orgs/<org-id>/custom-storage --data '{"name": "new-custom-storage", "access_key": "<access-key>", "secret_key": "<secret-key>", "bucket": "new-custom-storage", "endpoint_url": "https://s3-provider.example.com/"}'
1515
```
1616

17-
If desired, the `provider` field can be set to any of the [values supported by rclone for S3 providers](https://rclone.org/s3/#s3-provider). By default, this field is set to "Other", which should work for nearly all S3 storage providers. This value is used solely for migrations from rclone when updating org storage and/or replica locations.
17+
If desired, the `provider` field can be set to any of the [values supported by rclone for S3 providers](https://rclone.org/s3/#s3-provider). By default, this field is set to "Other", which should work for nearly all S3 storage providers. This value is used solely for migrating existing files with rclone when updating org storage and/or replica locations.
1818

1919
Verify that the custom storage has been added to the organization by checking the `/all-storages` API endpoint:
2020

0 commit comments

Comments
 (0)