(chore) Settings cog icon --> settings icon (#1623)

docs/authentication/configuration/sign-up-sign-in-options.mdx

@@ -144,7 +144,7 @@ To configure verification methods:
 
 1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username) and select your application.
 1. In the navigation sidebar, select **User & Authentication > Email, Phone, Username**.
-1. Select the settings cog icon next to the identifier, such as **Email address** or **Phone number**, to open the configuration settings.
+1. Select the settings icon next to the identifier, such as **Email address** or **Phone number**, to open the configuration settings.
 1. Under the **Verification methods** section, toggle on the verification methods you would like to enable.
 1. Select **Continue** to save your changes.
 

docs/authentication/saml/account-linking.mdx

@@ -28,7 +28,7 @@ To allow unverified email addresses for your instance:
 
 1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username)
 1. In the navigation sidebar, select **Email, Phone, Username**.
-1. Next to **Email address**, select the settings cog icon and uncheck the **Verify at sign-up** toggle.
+1. Next to **Email address**, select the settings icon and uncheck the **Verify at sign-up** toggle.
 
 When a user signs into your app using a SAML provider, Clerk links the SAML account to the existing account by also verifying the existing email address and signs the user in. This even applies to password-protected accounts, as the SAML sign-in process automatically bypasses password verification.
 

docs/authentication/saml/custom-provider.mdx

@@ -81,7 +81,7 @@ Clerk supports Enterprise SSO via the SAML protocol, enabling you to create auth
   1. In your IdP dashboard, paste the values in the appropriate fields.
 
   > [!TIP]
-  > If you closed your connection's configuration page in the Clerk Dashboard, you can find it by navigating to the [SSO Connections](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) page and selecting the settings cog icon next to the connection you want to configure.
+  > If you closed your connection's configuration page in the Clerk Dashboard, you can find it by navigating to the [SSO Connections](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) page and selecting the settings icon next to the connection you want to configure.
 
   ### Map your IdP's claims to Clerk fields
 

docs/authentication/social-connections/account-linking.mdx

@@ -25,7 +25,7 @@ In this scenario, when a user with a verified email address at Clerk signs in us
 
 For instances that allow account creation without email verification at sign-up, there is a possibility that an account may be created using an unverified email address, either through OAuth or other methods like username/password.
 
-To allow unverified email addresses for your instance, navigate to the [Email, Phone, Username](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username) page in the Clerk Dashboard. Click on the settings cog icon next to "Email address" and uncheck the "Verify at sign-up" toggle.
+To allow unverified email addresses for your instance, navigate to the [Email, Phone, Username](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username) page in the Clerk Dashboard. Click on the settings icon next to "Email address" and uncheck the "Verify at sign-up" toggle.
 
 ![Verify at sign-up toggle in the Clerk Dashboard](/docs/images/authentication/account-linking-verify-at-sign-up.webp)
 

docs/authentication/social-connections/x-twitter.mdx

@@ -66,7 +66,7 @@ Clerk does not currently support preconfigured shared OAuth credentials for X/Tw
   Go back to the Clerk Dashboard, where the modal should still be open, and paste these values into the respective fields.
 
   > [!NOTE]
-  > If the modal or page is not still open, navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Next to **X/Twitter**, select the settings cog icon. Under **Use custom credentials**, you can paste the **Client ID** and **Client Secret** into their respective fields.
+  > If the modal or page is not still open, navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Next to **X/Twitter**, select the settings icon. Under **Use custom credentials**, you can paste the **Client ID** and **Client Secret** into their respective fields.
 
   ### Test your OAuth
 

docs/authentication/web3/coinbase-wallet.mdx

@@ -44,7 +44,7 @@ To collect additional information about your user during sign-up:
 
 1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/web3).
 1. In the top navigation, select **Configure**. Then in the sidebar, select **[Email, phone, username](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username)**.
-1. On this page, toggle on attributes you wish to collect from your user during sign up. Select the settings cog icon next to an attribute to set it as **Required**. When set as **Required**, Clerk automatically prompts the user for this information after they authenticate with Coinbase Wallet.
+1. On this page, toggle on attributes you wish to collect from your user during sign up. Select the settings icon next to an attribute to set it as **Required**. When set as **Required**, Clerk automatically prompts the user for this information after they authenticate with Coinbase Wallet.
 
 ## Connect Coinbase Wallet to existing account
 

docs/custom-flows/email-links.mdx

@@ -46,7 +46,7 @@ Email link authentication can be configured through the Clerk Dashboard. Go to *
 
 Don't forget that you also need to make sure you've configured your application instance to request the user's email address. Users can receive email links only via email messages. Make sure you toggle on **Email address** under the **Contact information** section.
 
-If you click on the **Settings cog** icon next to **Email address**, the email address configuration screen will pop open. You can toggle on **Require** if you want to make sure that all users have an email address associated with their profile.
+If you click on the **Settings** icon next to **Email address**, the email address configuration screen will pop open. You can toggle on **Require** if you want to make sure that all users have an email address associated with their profile.
 
 You can also find the **Verification methods** section on this screen. Here, you can toggle on **Email verification link** if you would like to allow your users to verify their email with an email link. You can also toggle on **Email verification code** if you would like to allow your users to verify their email with a one-time passcode.
 

docs/custom-flows/email-password-mfa.mdx

@@ -21,7 +21,7 @@ This guide will walk you through how to build a custom email/password sign-in fl
 
   1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username).
   1. In the navigation sidebar, select **User & Authentication > Email, Phone, and Username**.
-  1. Ensure that _only_ **Email address** is required. If **Phone number** and **Username** are enabled, ensure they are not required. Use the settings cog icon next to each user attribute to check if a setting is required or optional. If you want to require **Username**, you must collect the username and pass the data to the `create()` method in your custom flow.
+  1. Ensure that _only_ **Email address** is required. If **Phone number** and **Username** are enabled, ensure they are not required. Use the settings icon next to each user attribute to check if a setting is required or optional. If you want to require **Username**, you must collect the username and pass the data to the `create()` method in your custom flow.
   1. In the **Authentication strategies** section of this page, ensure **Password** is enabled.
 
   ### Enable multi-factor authentication

docs/custom-flows/email-password.mdx

@@ -17,7 +17,7 @@ This guide will walk you through how to build a custom email/password sign-up an
 
   1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username).
   1. In the navigation sidebar, select **User & Authentication > Email, Phone, and Username**.
-  1. Ensure that _only_ **Email address** is required. If **Phone number** and **Username** are enabled, ensure they are not required. Use the settings cog icon next to each option to verify if a setting is required or optional. If you would like to require **Username**, you must collect the username and pass it to the `create()` method in your custom flow.
+  1. Ensure that _only_ **Email address** is required. If **Phone number** and **Username** are enabled, ensure they are not required. Use the settings icon next to each option to verify if a setting is required or optional. If you would like to require **Username**, you must collect the username and pass it to the `create()` method in your custom flow.
   1. In the **Authentication strategies** section of this page, ensure **Password** is enabled.
 
   > [!NOTE]

docs/custom-flows/email-sms-otp.mdx

@@ -19,7 +19,7 @@ This guide will walk you through how to build a custom SMS OTP sign-up and sign-
 
   1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username).
   1. In the navigation sidebar, go to **User & Authentication > Email, Phone, Username**.
-  1. Ensure that _only_ **Phone number** is required. If **Email address** or **Username** are enabled, ensure they are not required. Use the settings cog icon to check if a setting is required or optional. If you would like to require **Username**, you must collect the username and pass it to the `create()` method in your custom flow. For this guide, if you would like to use email OTP instead, require the **Email address** option instead of the **Phone number** option.
+  1. Ensure that _only_ **Phone number** is required. If **Email address** or **Username** are enabled, ensure they are not required. Use the settings icon to check if a setting is required or optional. If you would like to require **Username**, you must collect the username and pass it to the `create()` method in your custom flow. For this guide, if you would like to use email OTP instead, require the **Email address** option instead of the **Phone number** option.
   1. In the **Authentication strategies** section of this page, ensure **SMS verification code** is enabled. Ensure **Password** is toggled off, as you are prioritizing passwordless, SMS OTP-only authentication in this guide. If you would like to use email OTP instead, enable the **Email verification code** strategy instead of the **SMS verification code** strategy.
 
   ### Sign-up flow

docs/guides/transferring-your-app.mdx

@@ -18,7 +18,7 @@ To set up a payment method without being charged:
 > This guide offers a temporary solution for this issue. Clerk is actively working to improve this process.
 
 1. Switch to the receiving organization and open the organization switcher at the top-left of the Dashboard.
-1. Select the cog icon (⚙) to manage your organization.
+1. Select the settings icon to manage your organization.
 1. In the sidebar, select **Billing**, then select **Upgrade to unlimited members**.
 1. Add your billing information. **You will not be charged immediately**. Doing this just ensures billing information is added to the organization.
 1. Once that billing information is added, you will be able to transfer your Clerk app to the receiving organization.

docs/organizations/organization-workspaces.mdx

@@ -20,7 +20,7 @@ This guide will walk you through how to use the Clerk Dashboard to create an org
 ## Invite collaborators to your organization workspace
 
 1. Navigate to the [Clerk Dashboard](https://clerk.com/dashboard).
-1. In the top left navigation, select the organization workspace and select the settings cog icon. A modal will appear with the organization profile.
+1. In the top left navigation, select the organization workspace and select the settings icon. A modal will appear with the organization profile.
 1. Select the **Members** tab and select the **Invite** button.
 1. Enter the email address of the collaborator you wish to invite and select the role you wish to assign to the collaborator. If inviting multiple collaborators at a time, ensure email addresses are separated by spaces or commas.
 1. Select **Send invitations**.

docs/organizations/overview.mdx

@@ -148,7 +148,7 @@ To configure your application's **Email address** settings:
 1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username).
 1. In the navigation sidebar, select **User & Authentication > Email, Phone, Username**.
 1. In the **Contact information** section, ensure that **Email address** is toggled on.
-1. Next to **Email address**, select the settings cog icon to configure the email address settings. Here, at least **Require** should be toggled on.
+1. Next to **Email address**, select the settings icon to configure the email address settings. Here, at least **Require** should be toggled on.
 
 ## Organization management
 

docs/security/password-protection.mdx

@@ -32,7 +32,7 @@ To configure this feature:
 
 1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active).
 1. In the navigation sidenav, select **User & Authentication > Email, Phone, Username**.
-1. In the **Authentication strategies** section, next to **Password**, select the settings cog icon.
+1. In the **Authentication strategies** section, next to **Password**, select the settings icon.
 1. You can enable or disable **Reject compromised passwords on sign-up or password change, powered by HaveIBeenPwned**.
 1. You can also enable or disable **Reject compromised passwords also on sign-in**. Learn more about this feature in the following section.