Skip to content

Commit abeb7f7

Browse files
committed
fix visual bugs
1 parent 08f728a commit abeb7f7

File tree

2 files changed

+4
-7
lines changed

2 files changed

+4
-7
lines changed

cloud-account/join-or-leave-an-organization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ If you already belong to an organization, and you want to join a new one you wil
3535

3636
Alternatively, for Elastic Cloud Hosted deployments, there's a possibility to migrate your deployments to the new organization through back up and restore operations. In such case:
3737

38-
1. Back up your deployments to any private repository so that you can restore them to your new organization. <-- we could add a link to https://www.elastic.co/guide/en/cloud/current/ec-custom-repository.html when the page gets migrated -->
38+
1. [Back up your deployments to any private repository](/deploy-manage/tools/snapshot-and-restore/ec-custom-repository.md) so that you can restore them to your new organization.
3939
2. Leave your current organization.
4040
3. Ask the administrator to invite you to the organization you want to join.
4141
4. Accept the invitation that you will get by email.

cloud-account/multifactor-authentication.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -108,12 +108,9 @@ You can explore the following workarounds:
108108
* Use the email MFA method, assuming all of your team members have access to the generic account or distribution list’s mailbox.
109109
* Keep using the generic account to log in and set up multifactor authentication [using an authenticator app](#ec-account-security-mfa-authenticator).
110110

111-
```
112-
During the setup, take a photo of the QR code, or note its numeric version, and share it across your team. This code is sensitive and should be stored and shared securely. For example, it should be stored in an encrypted place using a secure algorithm such as AES-256, and transmitted over a secure encrypted channel such as TLS 1.3.
113-
```
114-
```
115-
This QR code is the "base" number used by the Authenticator app to generate codes based on the current time. There is no danger of synchronization issues. However, there is risk of a breach if the QR code picture or number is compromised.
116-
```
111+
During the setup, take a photo of the QR code, or note its numeric version, and share it across your team. This code is sensitive and should be stored and shared securely. For example, it should be stored in an encrypted place using a secure algorithm such as AES-256, and transmitted over a secure encrypted channel such as TLS 1.3.
112+
113+
This QR code is the "base" number used by the Authenticator app to generate codes based on the current time. There is no danger of synchronization issues. However, there is risk of a breach if the QR code picture or number is compromised.
117114

118115

119116
**After I set up an MFA method, will I need to answer an MFA challenge every time I authenticate through Elastic Cloud?**

0 commit comments

Comments
 (0)