first revision of updated react sdk refs

Author: KeeganBeuthin

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

@@ -78,15 +78,13 @@ There are different steps depending on the authentication method you use. Update
 
 ### Social sign in
 
-Add the `connection_id` to the auth url. Here is an example using React:
+Add the `connectionId` to the auth url. Here is an example using React:
 
 ```jsx
 <button
   onClick={() =>
     login({
-      authUrlParams: {
-        connection_id: "conn_6a95dec504d34dc286dc80e8df9f6099"
-      }
+      connectionId: "conn_6a95dec504d34dc286dc80e8df9f6099"
     })
   }
 >
@@ -98,7 +96,7 @@ You can now test if it works by signing in to your project or app.
 
 ### Email sign in
 
-Add the `connection_id` and `login_hint` params to the auth url.
+Add the `connectionId` and `loginHint` params to the auth url.
 
 The `login_hint` enables you to pre-populate the email for the user, skipping the step where they have to enter their identity/email. It also tells us where to send their one time password for passwordless verification.
 
@@ -108,10 +106,8 @@ Here is an example using React.
 <button
     onClick={() =>
       login({
-        authUrlParams: {
-            connection_id: "conn_e5f80aa5258e4685bf629b38003ee954"
-            login_hint: "[email protected]"
-         }
+        connectionId: "conn_e5f80aa5258e4685bf629b38003ee954",
+        loginHint: "[email protected]"
       })
     }
 >
@@ -123,22 +119,20 @@ You can now test if it works by signing in to your project or app.
 
 ### Phone sign in
 
-Add `connection_id` and `login_hint` params to the auth url.
+Add `connectionId` and `loginHint` params to the auth url.
 
-The `login_hint` enables you to pre-populate the phone for the user, skipping the step where they have to enter their phone number. It also tells us where to send their one time password for passwordless verification.
+The `loginHint` enables you to pre-populate the phone for the user, skipping the step where they have to enter their phone number. It also tells us where to send their one time password for passwordless verification.
 
-The `login_hint` needs to be in one of these formats `phone:<intl_number>:<country_code>` or `phone:<+intl_number>:<country_code>`. The ‘+’ symbol is optional, as long as the country code is included.
+The `loginHint` needs to be in one of these formats `phone:<intl_number>:<country_code>` or `phone:<+intl_number>:<country_code>`. The ‘+’ symbol is optional, as long as the country code is included.
 
 Here is an example using React:
 
 ```jsx
 <button
     onClick={() =>
       login({
-        authUrlParams: {
-          connection_id: "conn_e1d49977648149a2a32fde844f1ff9e5"
-          login_hint: "phone:+61466043123:au"
-        }
+          connectionId: "conn_e1d49977648149a2a32fde844f1ff9e5"
+          loginHint: "phone:+61466043123:au"
       })
     }
 >
@@ -150,15 +144,13 @@ You can now test if it works by signing in to your project or app.
 
 ### Enterprise sign in (Entra ID or SAML)
 
-Add the `connection_id` to the auth url. This takes the user directly to the enterprise authentication process. Here is an example using React:
+Add the `connectionId` to the auth url. This takes the user directly to the enterprise authentication process. Here is an example using React:
 
 ```jsx
 <button
   onClick={() =>
     login({
-      authUrlParams: {
-        connection_id: "conn_6a95dec504d34dc286dc80e8df9f6099"
-      }
+      connectionId: "conn_6a95dec504d34dc286dc80e8df9f6099"
     })
   }
 >

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

@@ -68,9 +68,9 @@ In this example, we’ve also included a check to see if this is the current org
 const {getClaim, getOrganization} = useKindeAuth();
 
 <ul>
-  {getClaim("organizations", "id_token").value.map((item) => (
+  {getClaim("organizations", "idToken").value.map((item) => (
     <li key={item.id}>
-      <button onClick={() => login({org_code: item.id})} type="button">
+      <button onClick={() => login({orgCode: item.id})} type="button">
         {item.name}
         {getOrganization().orgCode === item.id ? " (Current)" : null}
       </button>

src/content/docs/build/applications/authenticating-spa.mdx

@@ -30,11 +30,11 @@ This application type does not have a client secret as authentication takes plac
 4. This sample is from a React application, but it will be very similar for any frontend technology.
 
    ```jsx
-   const {getToken} = useKindeAuth();
+   const { getAccessToken } = useKindeAuth();
 
    const fetchData = async () => {
      try {
-       const accessToken = await getToken();
+       const accessToken = await getAccessToken();
        const res = await fetch(`<your_api_endpoint>`, {
          headers: {
            Authorization: `Bearer ${accessToken}`
@@ -52,7 +52,7 @@ This application type does not have a client secret as authentication takes plac
 
 You do not need to set up a back-end application in Kinde. The request sent to your API will include the access token, which gets validated when you receive it on your back end.
 
-Validation checks the token has not expired and that the token has originated from Kinde, as well as various other checks. While it is possible to write code to check this yourself, it can be easy to miss something and accidentally introduce serious security vulnerabilities. Here’s our recommendations:
+Validation checks the token has not expired and that the token has originated from Kinde, as well as various other checks. While it is possible to write code to check this yourself, it can be easy to miss something and accidentally introduce serious security vulnerabilities. Here's our recommendations:
 
 - Use the Kinde JWT verifier for your chosen technology (if available). Our Node package is available [here](https://www.npmjs.com/package/@kinde/jwt-validator).
 
@@ -62,7 +62,7 @@ OR
 
 OR
 
-- Choose a third-party library, for example the OpenID Foundation has [a list of libraries for working with JWT tokens](https://openid.net/developers/jwt/).
+- Choose a third-party library, for example the OpenID Foundation has [a list of libraries for working with JWT tokens](https://openid.net/developers/jwt/).
 
 #### Audience
 

src/content/docs/developer-tools/your-apis/protect-your-api.mdx

@@ -27,12 +27,12 @@ This ensures the access token you receive when the user signs in, will contain t
 When you make the call to your API you will want to ensure the access token is sent in the headers. An example in React for a bookstore app might be:
 
 ```jsx
-const {getToken} = useKindeAuth();
+const { getAccessToken } = useKindeAuth();
 const [books, setBooks] = useState([]);
 
 const fetchBooks = async () => {
   try {
-    const accessToken = await getToken();
+    const accessToken = await getAccessToken();
     const res = await fetch(`https://api.myapp.com/books`, {
       headers: {
         Authorization: `Bearer ${accessToken}`

src/content/docs/properties/work-with-properties/marketing-tags-properties.mdx

@@ -32,32 +32,32 @@ Contains the following properties:
 Contains the following properties:
 
 * Google ID `gclid`
-* Google click ID `click_id`
-* HSA account `hsa_acc`
-* HSA campaign `hsa_cam`
-* HSA group `hsa_grp`
-* HSA ad `hsa_ad`
-* HSA source `hsa_src`
-* HSA target `hsa_tgt`
-* HSA keyword `hsa_kw`
-* HSA match type `hsa_mt`
-* HSA network `hsa_net`
-* HSA version `hsa_ver`
+* Google click ID `clickId`
+* HSA account `hsaAßcc`
+* HSA campaign `hsaCam`
+* HSA group `hsaGrp`
+* HSA ad `hsaAd`
+* HSA source `hsaSrc`
+* HSA target `hsaTgt`
+* HSA keyword `hsaKw`
+* HSA match type `hsaMt`
+* HSA network `hsaNet`
+* HSA version `hsaVer`
 
 ### Marketing category
 
 Contains the following properties:
 
-* Match type `match_type`
+* Match type `matchType`
 * Keyword `keyword`
 * Device `device`
-* Ad group `ad_group_id`
-* Campaign ID `campaign_id`
+* Ad group `adGroupId`
+* Campaign ID `campaignId`
 * Creative `creative`
 * Network `network`
-* Ad position `ad_position`
+* Ad position `adPosition`
 * Facebook ID `fbclid`
-* LinkedIn ID `li_fat_id`
+* LinkedIn ID `liFatId`
 * Microsoft ID `msclkid`
 * X ID `twclid`
 * TikTok ID `ttclid`
@@ -68,21 +68,19 @@ There are a few mechanisms for updating these property values in Kinde.
 
 ### Pass the tracking tags via the auth flow
 
-This is the most common method. For example, if you want to pass in the UTM source, you just need to forward the `utm_source` query parameter as part of the sign up flow authentication url. Most of our SDKs allow you to pass this in via additional URL params. 
+This is the most common method. For example, if you want to pass in the UTM source, you just need to forward the `utmSource` query parameter as part of the sign up flow authentication url. Most of our SDKs allow you to pass this in via additional URL params. 
 
 For example in the React SDK:
 
 ```jsx
 <RegisterLink
   className="btn btn-dark"
-  authUrlParams={{
-    utm_source: "my source",
-   utm_medium: "some medium",
-   utm_campaign: "awesome campaing",
-   utm_content: "something else",
-   utm_term: "my terms",
-   click_id: "1234",
-}}
+    utmSource: "my source",
+   utmMedium: "some medium",
+   utmCampaign: "awesome campaing",
+   utmContent: "something else",
+   utmTerm: "my terms",
+   clickId: "1234",
 >Register</RegisterLink>
 ```