From f41b79a0698acb3f9e3eda72b839bb46b9308998 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Wed, 8 Jul 2020 13:12:36 -0700 Subject: [PATCH] Change back end to backend --- .../rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md b/content/rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md index 39400b87fbd..f1cfefeec90 100644 --- a/content/rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md +++ b/content/rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md @@ -63,7 +63,7 @@ The `--access-key` and `--secret-key` options are not required if the `etcd` nod _Available as of v0.2.0_ -The backup snapshot can be stored on a custom `S3` backup like [minio](https://min.io/). If the S3 backend uses a self-signed or custom certificate, provide a custom certificate using the `--s3-endpoint-ca` to connect to the S3 back end. +The backup snapshot can be stored on a custom `S3` backup like [minio](https://min.io/). If the S3 backend uses a self-signed or custom certificate, provide a custom certificate using the `--s3-endpoint-ca` to connect to the S3 backend. ### IAM Support for Storing Snapshots in S3