reviewed PR after peer comments

Author: danidelcar

src/data/navigation/sections/graphql.js

@@ -1249,6 +1249,14 @@ module.exports = [
                 title: "Minicart",
                 path: "/graphql/payment-services-extension/workflows/minicart.md",
               },
+              {
+                title: "Vaulting a card during a checkout authorization",
+                path: "/graphql/payment-services-extension/workflows/vault-with-purchase.md",
+              },
+              {
+                title: "Vaulting a credit card without a purchase",
+                path: "/graphql/payment-services-extension/workflows/vault-without-purchase.md",
+              },
               {
                 title: "Vaulted card",
                 path: "/graphql/payment-services-extension/workflows/vaulted-card.md",

src/pages/graphql/payment-services-extension/workflows/vault-with-purchase.md

@@ -12,8 +12,8 @@ These steps describe the flow of requests and responses required to [vault a cre
 
 The following conditions must be true to vault a card during checkout:
 
-* The customer needs to be logged in.
 * You must have installed [Payment Services for Adobe Commerce](https://commercemarketplace.adobe.com/magento-payment-services.html) 2.10.0 or higher.
+* The customer must be logged in.
 
 ## Vault during checkout workflow
 
@@ -27,7 +27,7 @@ The following conditions must be true to vault a card during checkout:
 
 1. Adobe Commerce returns a `Cart` object.
 
-1. Run the [`createPaymentOrder`](../../payment-services-extension/mutations/create-payment-order.md) mutation with `vaultIntent`set to `true` to begin the authorization process.
+1. Run the [`createPaymentOrder`](../../payment-services-extension/mutations/create-payment-order.md) mutation with `vaultIntent` set to `true` to begin the authorization process.
 
 1. Commerce forwards the request to PayPal.
 
@@ -93,7 +93,7 @@ mutation {
   "data": {
     "setPaymentMethodOnCart": {
       "cart": {
-        "id": "r8TKHa58b7Y8VaZHLyABNxrEdS8hJJTZ",
+        "id": "uocGxUi5H97XFAMhY3s66q4aFYG3Bmdr",
         "selected_payment_method": {
           "code": "payment_services_paypal_hosted_fields"
         }

src/pages/graphql/payment-services-extension/workflows/vault-without-purchase.md

@@ -20,7 +20,7 @@ These steps describe the flow of requests and responses required to [vault a pay
 
 1. Run the  [`createVaultCardSetupToken`](../../payment-services-extension/mutations/create-vault-card-setup-token.md) mutation to create a temporary `setup_token` associated to the given payment source.
 
-1. Commerce forwards token request to Paypal.
+1. Commerce forwards token request to PayPal.
 
 1. PayPal returns the temporary `setup_token` to Commerce.
 
@@ -40,6 +40,6 @@ These steps describe the flow of requests and responses required to [vault a pay
 
 The setup token is generated with an empty card number in the `payment_source` object purposefully. The PayPal SDK, in conjunction with hosted fields or credit cards field components, securely updates the setup token with payment details.
 
-See [Paypal SDK developer documentation](https://developer.paypal.com/docs/multiparty/checkout/save-payment-methods/purchase-later/js-sdk/cards/) for more information.
+See [PayPal SDK developer documentation](https://developer.paypal.com/docs/multiparty/checkout/save-payment-methods/purchase-later/js-sdk/cards/) for more information.
 
 To run the `createVaultCardPaymentToken` mutation, use the `setup_token` generated by the [`createVaultCardSetupToken`](../mutations/create-vault-card-setup-token.md) mutation.