make minor updates to auth docs

docs/documentation/platform/identities/universal-auth.mdx

@@ -33,7 +33,7 @@ using the Universal Auth authentication method.
     Now input a few details for your new identity. Here's some guidance for each field:
 
     - Name (required): A friendly name for the identity.
-    - Role (required): A role from the **Organization Roles** tab to permit the identity to access certain resources.
+    - Role (required): A role from the **Organization Roles** tab for the identity to assume. The organization role assigned will determine what organization level resources this identity can have access to.
     
     Once you've created an identity, you'll be prompted to configure the **Universal Auth** authentication method for it.
     
@@ -41,11 +41,11 @@ using the Universal Auth authentication method.
     
     Here's some more guidance on each field:
 
-    - Access Token TTL (default is `7200`): The incremental lifetime for an acccess token in seconds; a value of `0` implies an infinite incremental lifetime.
-    - Access Token Max TTL (default is `2592000`): The maximum lifetime for an acccess token in seconds; a value of `0` implies an infinite maximum lifetime.
+    - Access Token TTL (default is `2592000` equivalent to 30 days): The lifetime for an acccess token in seconds. This value will be referenced at renewal time.
+    - Access Token Max TTL (default is `2592000`  equivalent to 30 days): The maximum lifetime for an acccess token in seconds. This value will be referenced at renewal time.
     - Access Token Max Number of Uses (default is `0`): The maximum number of times that an access token can be used; a value of `0` implies infinite number of uses.
-    - Client Secret Trusted IPs: The IPs or CIDR ranges that the **Client Secret** can be used from together with the **Client ID** to get back an access token. By default, **Client Secrets** are given the `0.0.0.0/0` entry representing all possible IPv4 addresses.
-    - Access Token Trusted IPs: The IPs or CIDR ranges that access tokens can be used from. By default, each token is given the `0.0.0.0/0` entry representing all possible IPv4 addresses.
+    - Client Secret Trusted IPs: The IPs or CIDR ranges that the **Client Secret** can be used from together with the **Client ID** to get back an access token. By default, **Client Secrets** are given the `0.0.0.0/0`, allowing usage from any network address.
+    - Access Token Trusted IPs: The IPs or CIDR ranges that access tokens can be used from. By default, each token is given the `0.0.0.0/0`, allowing usage from any network address.
 
     <Warning>
     Restricting **Client Secret** and access token usage to specific trusted IPs is a paid feature.
@@ -75,7 +75,7 @@ using the Universal Auth authentication method.
 
     To do this, head over to the project you want to add the identity to and go to Project Settings > Access Control > Machine Identities and press **Add identity**.
 
-    Next, select the identity you want to add to the project and the role you want to assign it.
+    Next, select the identity you want to add to the project and the project level role you want to allow it to assume. The project role assigned will determine what project level resources this identity can have access to.
 
     ![identities project](../../images/platform/identities/identities-project.png)
     
@@ -101,6 +101,7 @@ using the Universal Auth authentication method.
     {
       "accessToken": "...",
       "expiresIn": 7200,
+      "accessTokenMaxTTL": 43244
       "tokenType": "Bearer"
     }
     ```
@@ -112,7 +113,7 @@ using the Universal Auth authentication method.
       the default TTL is `7200` seconds which can be adjusted.
 
       If an identity access token expires, it can no longer authenticate with the Infisical API. In this case,
-      a new access token should be obtained from the aforementioned login operation.
+      a new access token should be obtained by performing another login operation.
     </Note>
   </Step>
 </Steps>
@@ -128,13 +129,12 @@ using the Universal Auth authentication method.
   - You are attempting to access a `/raw` secrets endpoint that requires your project to disable E2EE.
   - The client secret/access token is being used from an untrusted IP.
 </Accordion>
-<Accordion title="What is token renewal and TTL/Max TTL?">
+<Accordion title="What is access token renewal and TTL/Max TTL?">
   A identity access token can have a time-to-live (TTL) or incremental lifetime afterwhich it expires.
   
-  In certain cases, you may want to extend the lifespan of an access token; to do so, you must use the max TTL parameter.
-  When TTL and max TTL are equal, a token is not renewable; when max TTL is greater than TTL, a token is renewable.
-  In the latter case, a token still expires at its TTL but its lifetime can be extended/renewed up until its max TLL.
-  
-  Note that the max TTL cannot be less than the TTL for an access token.
+  In certain cases, you may want to extend the lifespan of an access token; to do so, you must set a max TTL parameter.
+
+  A token can be renewed any number of time and each call to renew it will extend the toke life by increments of access token TTL. 
+  Regardless of how frequently an access token is renewed, its lifespan remains bound to the maximum TTL determined at its creation
 </Accordion>
 </AccordionGroup>