From a6b751346fca7f0824c3c6ad9d8eff51ce1e8931 Mon Sep 17 00:00:00 2001
From: Carl Dunkelberger <39133599+cdunkelb@users.noreply.github.com>
Date: Tue, 8 Oct 2019 12:05:54 -0400
Subject: [PATCH] Updating number of files in the backup tar (#9506)

---
 ee/admin/backup/back-up-ucp.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ee/admin/backup/back-up-ucp.md b/ee/admin/backup/back-up-ucp.md
index 6980e0a3ea..bd49c1df16 100644
--- a/ee/admin/backup/back-up-ucp.md
+++ b/ee/admin/backup/back-up-ucp.md
@@ -118,7 +118,7 @@ $ docker container run \
 To view backup progress and error reporting, view the contents of the stderr streams of the running backup container during the backup. Progress is updated for each backup step, for example, after validation, after volumes are backed up, after `etcd` is backed up, and after `rethinkDB`. Progress is not preserved after the backup has completed. 
 
 #### Verify a UCP backup
-In a valid backup file, more than 100 files are displayed in the list and the `./ucp-node-certs/key.pem` file is present. Ensure the backup is a valid tar file by listing its contents, as shown in the following exampele: 
+In a valid backup file, 27 or more files are displayed in the list and the `./ucp-controller-server-certs/key.pem` file is present. Ensure the backup is a valid tar file by listing its contents, as shown in the following exampele: 
 
 ```
 $ gpg --decrypt /directory1/directory2/backup.tar | tar --list