Just nitpicks, but I think that there is still room for simplifying the structure and improving the readability.
I'm suggesting the following:

• remove the slash from every place, where it doesn't fulfil the role of an alternative - scenario/example; recommended settings/keycloak configuration; beginner/quick - all have very similar meaning in this context,
• on the other hand, let's add more precise, more detailed descriptions; use rather full sentence instead of collocations separated by commas,
• remove the bullet points - if you need, break the line instead,
• use either bold or italic text (not both at the same time).

Here's what I mean by that:

Regardless, I'm not sure, whether it's worth to mention this particular scenario, as it doesn't provide any additional information regarding the hostname setup (compared to others bellow). But it's up to a discussion, I used it as a reference example of how the format could be potentially improved.

Ok. In the regard of simplifying the format, suggestions accepted and applied. Thanks.

• remove the slash from every place, where it doesn't fulfil the role of an alternative - scenario/example; recommended settings/keycloak configuration; beginner/quick - all have very similar meaning in this context,

  • Done. Please review again If it is better this way.

• on the other hand, let's add more precise, more detailed descriptions; use rather full sentence instead of collocations separated by commas

  • What is your suggestion of full sentence, where do you think it is not good?

• remove the bullet points - if you need, break the line instead

  • Done.

• use either bold or italic text (not both at the same time).

  • Done.

• Regardless, I'm not sure, whether it's worth to mention this particular scenario, as it doesn't provide any additional information regarding the hostname setup (compared to others bellow). But it's up to a discussion, I used it as a reference example of how the format could be potentially improved.

  • Exactly. In my view, the most important points of this review are: Evaluate which scenarios make sense to mention in this Guide and If the kc start command options are right for each scenario. And I need your help in this effort.

Thanks.

What is your suggestion of full sentence, where do you think it is not good?

I meant it rather like a reminder that we should avoid sentence structures like the one you use initially:
The most basic option to run, in localhost, all default values.

Anyway, I think that right now the rest is ok. Thanks!

@andre-nascimento-rh I asked about this above, in my earlier comments - is there a reason to capitalize the keywords like Proxy, Hostname, Edge etc? Unless they're the part of a heading, I would use lowercase as in normal sentence.

Also, there is lot of inconsistency in using pre-formated text (text enclosed into the backticks). Sometimes you use it, sometimes you don't. We need to be more consistent and I would suggest to not to overuse it.

Moreover, in this specific case the description consists of two sentences, which are synonymous. Please, rephrase it.

Double-checked and changed the leaving capitalized words.

I see that you didn't fully accepted my previous suggestion - that's ok, just please be careful about the consistency. even when in the headings. Check the existing examples in the Hostname Configuration Guide.
So I would do at least these adjustments:

Sorry, but it exactly the opposite: I accepted almost all of your suggestions. I applied the change at the adoc file and pushed it. I understood that using capitalized words in titles there wasn't an issue for you. But now I'm changing all the titles. No problem.

@andre-nascimento-rh I meant this specific suggestion that covered just the fist scenario. In the suggestion I deliberately changed the heading in a way that it doesn't contain uppercase letters (and also the wording is little bit different). I noticed that you didn't apply it (which is totally fine), but we need to stay consistent.

I don't even have strong preference, whether the first letter of a word in the heading should be uppercase or not (it was my natural suggestion to stay consistent with what we already have but in the end it's up to your own style), just the consistency hasn't been there yet. Therefore I reminded it. 😊

I applied what you suggested. Are you seeing the last version?

Explained and resolved offline.

We are mentioning the necessity to setup TLS for HTTPS scenarios (for the production mode) right at the beginning. Is it necessary to repeat the same in the descriptions of the particular scenarios?

Yes, I believe it is clearer.

ok, then we should at least correct the capital letter in "Certificates".

Btw, this is a good example where I would use an additional formatting to highlight "not recommended part".

Done. Review it If that way suits your expectation.

What I meant by this suggestion was to get rid of the bracket part (the capital letter and exclamation mark specifically).

And during the process I thought also about minimizing the usage of second-person pronouns (e.g. you) and possessive pronouns (e.g. your). But I would rather leave this opened for someone with better linguistic knowledge.