Apply suggestions from code review

Co-authored-by: josef <[email protected]>

Author: jjarvisp

src/pages/[platform]/build-a-backend/auth/concepts/multi-factor-authentication/index.mdx

@@ -887,7 +887,7 @@ If you are using the [Authenticator component](https://ui.docs.amplify.aws/andro
 </Callout>
 </InlineFilter>
 
-Once you have setup email as your second layer of authentication with MFA as shown above, your users will get an authentication code via an email to complete sign-in after they sign in with their username and password.
+Once you have setup email as your second layer of authentication with MFA as shown above, your users will get an authentication code via email to complete sign-in after they sign in with their username and password.
 
 <Callout warning>
 

src/pages/[platform]/build-a-backend/auth/multi-step-sign-in/index.mdx

@@ -2207,7 +2207,11 @@ func confirmSignIn(totpCode: String) -> AnyCancellable {
 ## Confirm signin with Email MFA
 If the next step is `confirmSignInWithOTP`, Amplify Auth has sent a random code to the user's email address, and is waiting to find out if the user successfully received it. To handle this step, your app's UI must prompt the user to enter the code. After the user enters the code, your implementation must pass the value to Amplify Auth `confirmSignIn` API.
 
-Note: the signin result also includes an `AuthCodeDeliveryDetails` member. It includes additional information about the code delivery such as the partial email address of the recipient.
+<Callout info>
+
+**Note:** the sign-in result also includes an `AuthCodeDeliveryDetails` member. It includes additional information about the code delivery such as the partial email address of the recipient.
+
+</Callout>
 
 <BlockSwitcher>