docs: 10180 Fix SDK

[brennhill]

Description

Closes: #10180 #10180

Fixes how we refer to the SDK throughout the documentation.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• [NA] followed the guidelines for building modules
• [NA] included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• [NA] included comments for documenting Go code
• [NA] updated the relevant documentation or specification
• [NA] reviewed "Files changed" and left comments if necessary
• [NA] confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[barriebyron]

oops @brennhill to make these types of changes more manageable, I had limited the scope in #10180

The scope of this GitHub issue and your PR is limited to the Cosmos SDK Introduction topic https://docs.cosmos.network/master/intro/ and child topics.

and had staged the issue to be used in October Codefest but am so so happy to see contributors jump in to make improvements no matter when they do the work!

can you take a look @aaronc and @alexanderbez ? please and thank you

[barriebyron]

@brennhill did you want to close this PR and then open a different PR in the month of October, and please limit your scope

[brennhill]

@barriebryon I could do that but I don't need to wait until october. If the changes are good I'd rather you go ahead and use them. It frees up my mind for other things.

[barriebyron]

@brennhill thanks for being willing to make these improvements! Sounds good to me, and I look forward to your continued contributions. Grab an issue during October if you want to participate in October Codefest.

Any fixes for the codebase are good fixes and we appreciate you!

[barriebyron]

so many good changes, thank you @brennhill can you check your "an" and make changes as required ?

[amaury1093]

lgtm

[barriebyron]

thank you so much for helping with our consistent branding, @brennhill!

[robert-zaremba]

For future reference, do we want to always put Cosmos next to SDK, even when we say "the SDK"?

[barriebyron]

For future reference, do we want to always put Cosmos next to SDK, even when we say "the SDK"?

yes @robert-zaremba we do! Branding, especially in docs, is essential. Using the full "Cosmos SDK" is essential. For example, when a bit of a doc gets shared in the world at large, we want to make sure our reader knows "the SDK" is "the Cosmos SDK"

Thanks for asking!