fix:minor edits to gravity-dex.md

[barriebyron]

Applied several editorial standards throughout the content, no substantive changes.
Doc is so improved! Good job, I am very excited to see this evolution.

Highlights

• use descriptive link text per https://developers.google.com/style/link-text
• use imperative language "do this" instead of "if you don't do this" (change timeouts)
• add space between number and unit of measure (8 GB RAM) https://developers.google.com/style/units-of-measure?hl=en
• use following instead of below, https://developers.google.com/style/word-list?hl=en#letter-b

[barriebyron]

@kogisin thanks for looking at these editorial changes!

[barriebyron]

instead of "Replace necessary configuration" I think we're saying to run these commands?

[jaybxyz]

Yes. I think it is better.

[barriebyron]

@kogisin I see the repo is still not protected, can we fix that?

[jaybxyz]

@barriebyron Thanks for looking into this docs! As always, your feedback and suggestions are very helpful.

I see the repo is still not protected, can we fix that?

What do you mean by "not protected"? Can you elaborate?

[barriebyron]

@barriebyron Thanks for looking into this docs! As always, your feedback and suggestions are very helpful.

I see the repo is still not protected, can we fix that?

What do you mean by "not protected"? Can you elaborate?

Hi @kogisin I had the option to merge the PR without any approvals (oops). The repo is brand new, I see. I had the distinct pleasure to create PR 1. Best practice is to require approvals before allowing PRs to be merged into the main branch. See
https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule

and do you know about accepting the commit suggestions? You can go through one by one and add to batch so all changes apply to a single commit. You can even edit the suggestion before you accept or add to batch. https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request

[jaybxyz]

Like you said, the repo is brand new and I didn’t expect to collaborate with anyone anytime soon, but here you are. Thanks! I just added the protection rule for all branches. All PRs require at least 1 review and status checks need to be passed before merging.

[jaybxyz]

I did not know we need space between the number and gigabytes. Is this conventional?

[jaybxyz]

We need to locate the field down to part 2 since part 1 only deals with setting up the peers list.

# The ibc and swap state are very large, causing the node itself 
# to stop on excessive queries. Therefore, we customize the rpc configuration 
# as above.

# How long to wait for a tx to be committed during /broadcast_tx_commit.
# WARNING: Using a value larger than 10s will result in increasing the
# global HTTP write timeout, which applies to all connections and endpoints.
# See https://github.com/tendermint/tendermint/issues/3435
timeout_broadcast_tx_commit = "600s"