docs: clarify graceful refresh token rotation

[aeneasr]

Related Issue or Design Document

Checklist

• I have read the contributing guidelines and signed the CLA.
• I have referenced an issue containing the design document if my change introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security vulnerability.
  If this pull request addresses a security vulnerability,
  I confirm that I got approval (please contact security@ory.sh) from the maintainers to push the changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation within the code base (if appropriate).

Further comments

[vinckr]

Please use bold only when writing about user interface (UI) elements.

[aeneasr]

Hm, I find the text on the left easier to read - is it not common to make the - text: part before the : bold to summarize the point?

[vinckr]

Hm, I find the text on the left easier to read - is it not common to make the - text: part before the : bold to summarize the point?

Maybe, but at the moment we follow the microsoft style guide which says bolding only in special cases such as describing UI.

We can change that, but it would need to be consistent across the whole documentation and documented clearly in the style guide.
What is no go in my opinion is everyone contributing to docs doing it in their own style and then its absolutely disjointed.

[aeneasr]

OK, thank you for updating it!

[alnr]

The phrase "consent request" is, I think, a Hydra implementation artifact.

Maybe some day we can clarify the concepts both in documenation and in code.

It's a difficult thing to wrap your head around. This is just a side remark.

This PR is 👍

[aeneasr]

Yeah, I actually struggled quite hard in trying to find the right phrase. Is it login request? consent request? token chain? consent flow? authorized consent id? Haven't found a good solution yet.