[documentation] revision of redis-hbo-provider.rst

[steveburnett]

Description

Noticed the numbering of the steps in Production Setup of Redis HBO Provider was out of order and fixed that. Also minor edits of punctuation, formatting, and links.

Motivation and Context

Readers might be confused by the step numbering.

Impact

Documentation.

Test Plan

Built docs locally and reviewed the local build of the page.

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

== NO RELEASE NOTE ==

[steveburnett]

@jaystarshot, I'd appreciate your review of my suggested changes to this docs page. Thanks!

[steveburnett]

Are there default values for these configuration properties that could be added to this table?

[jaystarshot]

I have added some defaults, most of the other config properties will need user enviroment specific changes

[jaystarshot]

Actually we can add a default column

[steveburnett]

Thanks! I added a default column in the second table - the four properties in "Coordinator Configuration for Historical Based Optimization", as you provided default values for all of them. Here's a screenshot of my local build showing the Default Value column added to that table.

I requested another review from you when you have time because I made this change after your first review.

[steveburnett]

Are there default values that could be documented for any of the eight properties in the first table (coordinator through hbo.redis-provider.cluster-mode-enabled)?

[jaystarshot]

Actually, we don't have a default value set as of now. I will try to add default values in a PR soon.
Would it work if we added a sample property column?

[jaystarshot]

I have added some examples below in the documentation though

[steveburnett]

Actually, we don't have a default value set as of now. I will try to add default values in a PR soon. Would it work if we added a sample property column?

I see the examples in the codeblock, those are a big help for the user.

Docs should describe the current state of the software - if the default values for those don't exist then we don't need to document them. When you add default values in a future PR, we can document those values at that time by updating this page as part of that PR. Does that seem reasonable?

[jaystarshot]

Thanks for the revision!

[jaystarshot]

I have added some defaults, most of the other config properties will need user enviroment specific changes