Apply suggestions from code review

Co-authored-by: Tyler-Larkin <[email protected]>

Author: jjarvisp

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

@@ -195,7 +195,7 @@ Future<void> _handleMfaSelection(MfaType selection) async {
     );
     return _handleSignInResult(result);
   } on AuthException catch (e) {
-    safePrint('Error resending code: ${e.message}');
+    safePrint('Error sending MFA selection: ${e.message}');
   }
 }
 ```
@@ -1007,8 +1007,8 @@ Future<void> signUpWithEmailVerification(
     password: password,
     options: SignUpOptions(
       userAttributes: <AuthUserAttributeKey, String>{
-        // ... if required
         AuthUserAttributeKey.email: '[email protected]',
+        // ... if required
         AuthUserAttributeKey.phoneNumber: '+18885551234',
       },
     ),

src/pages/[platform]/build-a-backend/auth/connect-your-frontend/sign-in/index.mdx

@@ -629,7 +629,7 @@ Following sign in, you will receive a `nextStep` in the sign-in result of one of
 | `confirmSignInWithSmsMfaCode` | The sign-in must be confirmed with a SMS code from the user. Complete the process with `confirmSignIn`. |
 | `confirmSignInWithOtpCode` | The sign-in must be confirmed with a code from the user (sent via SMS or Email). Complete the process with `confirmSignIn`. |
 | `continueSignInWithMfaSelection` | The user must select their mode of MFA verification before signing in. Complete the process with `confirmSignIn`. |
-| `continueSignInWithMfaSetupSelection` | The user must select their mode of MFA verification to setup. Complete the process by passing either `"EMAIL"` or `"TOTP"` to `confirmSignIn`. |
+| `continueSignInWithMfaSetupSelection` | The user must select their mode of MFA verification to setup. Complete the process by passing either `MfaType.email.confirmationValue` or `MfaType.totp.confirmationValue` to `confirmSignIn`. |
 | `continueSignInWithTotpSetup` | The TOTP setup process must be continued. Complete the process with `confirmSignIn`. |
 | `continueSignInWithEmailMfaSetup` | The EMAIL setup process must be continued. Complete the process by passing a valid email address to `confirmSignIn`. |
 </InlineFilter>

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

@@ -573,7 +573,7 @@ Future<void> _handleSignInResult(SignInResult result) async {
       // Handle select from MFA methods available to setup
     case AuthSignInStep.continueSignInWithEmailMfaSetup:
       // Handle email setup case
-    case AuthSignInStep.confirmSignInWithEmailMfaCode:
+    case AuthSignInStep.confirmSignInWithOtpCode:
       // Handle email MFA case
     case AuthSignInStep.continueSignInWithTotpSetup:
       // Handle TOTP setup case
@@ -669,7 +669,7 @@ Future<void> confirmTotpUser(String totpCode) async {
 
 ## Confirm signin with Email MFA
 
-If the next step is `confirmSignInWithEmailMfaCode`, Amplify Auth has sent the user a random code to their email address and is waiting for the user to verify that code. To handle this step, your app's UI must prompt the user to enter the code. After the user enters the code, pass the value to the `confirmSignIn` API.
+If the next step is `confirmSignInWithOtpCode`, Amplify Auth has sent the user a random code to their email address and is waiting for the user to verify that code. To handle this step, your app's UI must prompt the user to enter the code. After the user enters the code, pass the value to the `confirmSignIn` API.
 
 <Callout>
 
@@ -681,7 +681,7 @@ the recipient, which can be used to prompt the user on where to look for the cod
 ```dart
 Future<void> _handleSignInResult(SignInResult result) async {
   switch (result.nextStep.signInStep) {
-    case AuthSignInStep.confirmSignInWithEmailMfaCode:
+    case AuthSignInStep.confirmSignInWithOtpCode:
       final codeDeliveryDetails = result.nextStep.codeDeliveryDetails!;
       _handleCodeDelivery(codeDeliveryDetails);
     // ...