Fixing image alt code

Author: alex72508

src/content/docs/authenticate/authentication-methods/email-authentication.mdx

@@ -40,8 +40,8 @@ The verification email has limited customizations.
 - Email content references your [business] name in Kinde. For example:
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/c38710e9-889e-440e-5b6d-3421bb377900/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/c38710e9-889e-440e-5b6d-3421bb377900/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"

src/content/docs/authenticate/authentication-methods/username-authentication.mdx

@@ -49,8 +49,8 @@ Regardless of how a username is added, it must be unique (in more than case). If
 For security reasons, Kinde doesn’t allow fully anonymous users. So when a user signs up, they will need to supply an email, in addition to a username. The email can then be used to verify their identity. The username can be supplied by you, or can be created by the user.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/c4f7ed33-ef8b-442e-14f0-bc12a4f5c100/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/c4f7ed33-ef8b-442e-14f0-bc12a4f5c100/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"
@@ -65,8 +65,8 @@ When a user signs in, they enter their username and proceed with a [password](/a
 Either way, it’s a quick process for sign in.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/ce25d6b7-0e5c-4f0c-0851-996a8315fb00/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/ce25d6b7-0e5c-4f0c-0851-996a8315fb00/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"

src/content/docs/authenticate/custom-configurations/authentication-experience.mdx

@@ -27,8 +27,8 @@ Kinde aims to give you as much control of your user’s sign up and sign in expe
 You’ll find these in Kinde: **Settings > Applications > View details** on your application.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/f8d6db00-fa71-41d0-7c1c-630508f6c300/public
-  alt="Application switches for custom sign in behaviour
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/f8d6db00-fa71-41d0-7c1c-630508f6c300/public"
+  alt="Application switches for custom sign in behaviour"
   width="672px"
   height="auto"
   fetchpriority="low"

src/content/docs/authenticate/custom-configurations/custom-authentication-pages.mdx

@@ -38,8 +38,8 @@ If you only allow users to sign up and sign in with social authentication - such
 Users sign up or sign in from your custom screen, then get pushed straight through to the social provider’s account selection screen. For example:
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/20ed27ab-5a0a-47b5-b66e-025013c60400/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/20ed27ab-5a0a-47b5-b66e-025013c60400/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"
@@ -54,8 +54,8 @@ If you allow email sign up and sign in, the initial Kinde screen can be bypassed
 When a user signs up (say, via email), they do this in fields on your custom sign in screen. Then for verification, they see Kinde’s verification code screen. After that, it’s all you again.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/b08b9164-775c-4de7-669e-87ebaa329200/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/b08b9164-775c-4de7-669e-87ebaa329200/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"

src/content/docs/authenticate/custom-configurations/proxy-your-kinde-auth-pages-through-cloudflare.mdx

@@ -31,8 +31,8 @@ You can take advantage of Cloudflare’s advanced security features such as thei
 2. Set up DNS records for the domain in Cloudflare. We will change this from DNS once the records have been validated. DNS validation confirms the record before we set the proxy.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/11ab78a6-3b68-4424-2228-b45806f1a400/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/11ab78a6-3b68-4424-2228-b45806f1a400/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"
@@ -51,8 +51,8 @@ Leave the ACME challenge record as DNS. This is used to verify domain ownership
 </Aside>
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/1c91bc73-5252-4062-2bb0-af877e945200/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/1c91bc73-5252-4062-2bb0-af877e945200/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"
@@ -73,8 +73,8 @@ To test the proxied domain, create a WAF rule to show a Cloudflare Managed Chall
 For example, create a rule to match the hostname of the custom domain used in Kinde and the request originating from Australia. The action is to show a **Managed Challenge**.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/2aba2c16-a345-4179-3075-52485a126c00/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/2aba2c16-a345-4179-3075-52485a126c00/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"

src/content/docs/authenticate/manage-authentication/navigate-between-organizations.mdx

@@ -31,8 +31,8 @@ The first step is to include a list of organizations a user belongs to, in their
 2. Scroll down to the **Token customization** section and select **Configure** on the **ID token** card. The **Customize ID token** window opens.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/60ed313e-8250-4b33-0645-51a97ccc6d00/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/60ed313e-8250-4b33-0645-51a97ccc6d00/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"
@@ -93,8 +93,8 @@ const {getClaim, getOrganization} = useKindeAuth();
 With some extra styling, a switcher might look something like this:
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/762446ab-6ce7-4e6f-746f-d2ca87efee00/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/762446ab-6ce7-4e6f-746f-d2ca87efee00/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"

src/content/docs/authenticate/manage-authentication/user-auth-applications.mdx

@@ -53,8 +53,8 @@ See also [multi-domain authentication](/authenticate/about-auth/about-authentica
 Say you are signed into your **Admin app** and want to switch to the **Employee app**. Here’s how it might look.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/6a56c72a-21ea-4bc7-6b6d-f79efd1bda00/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/6a56c72a-21ea-4bc7-6b6d-f79efd1bda00/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"

src/content/docs/authenticate/social-sign-in/github.mdx

@@ -49,8 +49,8 @@ Before you make your production environment live, you must add your own social a
 9. (Recommended) In the **Permissions** section, open the **Account permissions** options and change the **Email addresses** access to **Read only**. This enables Kinde to more easily match up user accounts with access to all the users' email addresses.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/91a0d647-35d8-450b-26d2-21b5c8dca400/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/91a0d647-35d8-450b-26d2-21b5c8dca400/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"

src/content/docs/authenticate/social-sign-in/google.mdx

@@ -61,8 +61,8 @@ Before connecting Google as a sign in option, be aware that Google does not supp
 6. Select if your project is **Internal** or **External,** then select **Create**.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/412af691-19cd-45b2-3af7-f5db15677a00/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/412af691-19cd-45b2-3af7-f5db15677a00/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"
@@ -81,8 +81,8 @@ Before connecting Google as a sign in option, be aware that Google does not supp
 15. In the **Web application** dropdown menu, choose **Web Application**.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/3518f0a9-6232-41b8-2e37-0293fed41200/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/3518f0a9-6232-41b8-2e37-0293fed41200/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"

src/content/docs/build/domains/pointing-your-domain.mdx

@@ -100,8 +100,8 @@ The challenge DNS record needs to remain in place after verification in order fo
 When you use social connections to authenticate users, you need to add the callback URL to the provider app so that the custom domain shows on the sign in form, instead of kinde.com.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/9247cb87-9e7a-4977-b3f5-6c8b52f64200/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/9247cb87-9e7a-4977-b3f5-6c8b52f64200/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"
@@ -145,8 +145,8 @@ The details provided in the admin console assumes the domain entered is adding a
 So if your business is `multi.subdomain.example.com` and your zone is `example.com`, you need to create a DNS entry for `multi.subdomain`, as well as for `_acme-challenge.multi.subdomain`.
 
 <img
-  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/ee01b968-bea8-4082-7680-cde0522fbf00/public
-  alt="
+  src="https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/ee01b968-bea8-4082-7680-cde0522fbf00/public"
+  alt=""
   width="672px"
   height="auto"
   fetchpriority="low"