minor edits

product_docs/docs/biganimal/release/getting_started/identity_provider/aws_sso.mdx

@@ -18,12 +18,14 @@ description: "Using AWS SSO as your identity provider for your Azure account"
    !!! note
    You may need to switch to a region where SSO is enabled. AWS Organizations support SSO in only one region at a time.
    !!!
-1. From the left navigation pane, select **Applications** or select the link in Step 3 on the **Dashboard**. 
-1. On the Applications page, select **Add a new application". On the Add New Application page:
+1. Navigate to the Applications page by either selecting **Applications** from the left navigation pane or selecting the link in step 3 on the Welcome to AWS Single Sign-On page.
+1. On the Applications page, select **Add a new application**. On the Add New Application page:
    1. Select **Add a custom SAML 2.0 application**.
+
    1. Name the application in the **Display Name** field. The application will be visible to your users under this name.
 1. At the bottom of the page under **Application metadata**, select the link "If you don't have a metadata file...".
    1. Open the Set Up Identity Provider page in BigAnimal. 
+
    2. Copy the following information from BigAnimal and paste it into the Application metadata section. 
 
       | Copy from BigAnimal            | Paste into Application Metadata |
@@ -58,9 +60,11 @@ description: "Using AWS SSO as your identity provider for your Azure account"
 1. Go to the **Assigned users** tab and select the **Assign users** button to allow users access to the application. 
 1. Go to the **Configuration** tab and scroll down to the **AWS SSO metadata** section. 
    1. Copy the **AWS SSO sign-in URL**.
+
    2. Select **Download certificate** to install the AWS SSO certificate.
 1. On the Setup Identity Provider page in BigAnimal, select the **Setup Config** tab. 
    1. Paste the **AWS SSO sign in URL** into the **Single Sign-On URL** field. 
+
    1. Select **Choose File** and choose the **AWS SSO certificate** from your files. 
    1. Select HTTP-POST for the **Request Binding**.
    1. Enter a **Response Signature Algorithm**. We reccomend rsa-sha256.