Merge pull request #399 from kinde-oss/Fix/Small-doc-updates

Minor copy changes to SAML file and a workflow trigger file.

Author: clairekinde11

src/content/docs/authenticate/enterprise-connections/advanced-saml-configurations.mdx

@@ -62,6 +62,8 @@ Only configure key attributes if supported by your IdP.
 
 You can pass provider-specific parameters to an Identity Provider (IdP) during authentication. These are also known as 'upstream params'. The values your pass can either be static per connection or dynamic per user.
 
-You can use upstream paramsto create a smoother sign in experience - by passing the email through, or to offer an account switcher (such as the Google account switcher) during sign in.
+You can use upstream params to create a smoother sign in experience - by passing the email through, or to offer an account switcher (such as the Google account switcher) during sign in.
 
 Note that every identity provider has their own set of supported parameters and values, so you'll need to check their documentation to determine which URL parameters are supported.
+
+For more information, see [Pass parameters to identity providers](/authenticate/auth-guides/pass-params-idp/).

src/content/docs/workflows/example-workflows/new-password-provided-workflow.mdx

@@ -103,13 +103,13 @@ Example
 ```jsx
 const isMinCharacters = context.auth.firstPassword.length >= 50;
 
-kinde.widget.invalidateFormField("p_password_1", "Provide a password at least 50 characters long");
+kinde.widget.invalidateFormField("p_first_password", "Provide a password at least 50 characters long");
 
 ```
 
 The field names for this workflow are
 
 | Field name | Description |
 | --- | --- |
-| `p_password_1` | The first password field |
-| `p_password_2` | The second password field, typically to check it matches the first to help prevent typos |
+| `p_first_password` | The first password field |
+| `p_second_password` | The second password field, typically to check it matches the first to help prevent typos |