refactor: improve docs for rotate refresh token (#784)

* refactor: improve docs for rotate refresh token

* refactor: update per comments

Co-authored-by: Gao Sun <gao@silverhand.io>

---------

Co-authored-by: Gao Sun <gao@silverhand.io>

Author: charIeszhao

docs/docs/references/applications/README.mdx

@@ -111,16 +111,17 @@ However, this practice is discouraged unless necessary (usually it's useful for
 
 <Availability cloud oss={{ major: 1, minor: 6 }} />
 
-_Availability: Traditional web, Machine-to-machine; Default: `true`_
+_Default: `true`_
 
-When enabled, Logto will issue a new Refresh Token for token requests under the following conditions:
+When enabled, Logto will issue a new refresh token for token requests under the following conditions:
 
-- If the time elapsed since the refresh token was last rotated is less than 1 year; and
-- If 70% of the original Time to Live (TTL) has passed; or
-- If the client is a non-sender-constrained public client.
+- If the refresh token has been rotated (have its TTL prolonged by issuing a new one) for one year; **OR**
+- If the refresh token is close to its expiration time (>=70% of its original Time to Live (TTL) passed); **OR**
+- If the client is a public client, e.g. Native application or single page application (SPA).
 
 :::note
-If the application type is not available for this switch, it means a new refresh token will be always issued for each token request.
+For public clients, when this feature is enabled, a new refresh token will always be issued when the client is exchanging for a new access token using the refresh token.
+Although you can still turn off the feature for those public clients, it is highly recommended to keep it enabled for security reasons.
 :::
 
 ### Refresh Token Time to Live (TTL) in days