docs: improve documentation quality

[jaybxyz]

Summary

Documentation has areas for improvement. These are some of the areas that I am concerned with:

• Are there any typos or grammatical mistakes?
• How smooth an explanation is written?
• Is there consistency of documentation style?
• Is there any area where it should provide more information?
• ...

Proposal

Team Korea would be really grateful if @barriebyron could spare some time to review our documentation and help us to improve documentation quality.

Tasks

Completed Oct 21:

• proto/tendermint/farming/v1beta1/

  • edit farming.proto #187

• x/farming/spec

  • docs: edit farming spec to improve documentation quality (part of #172)  #191

• docs/Tutorial/demo/budget_with_farming.md

  • docs: edit budget_with_farming.md demo text #210

• docs/How-To/cli

  • docs: Update README.md farming edits #211

• docs/How-To/api

  • docs: update api README tiny edits #212

Delivered: Technical content style guidance for Farming

CODEOWNERS

• feat: Create CODEOWNERS file and update contributing.md #189

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[jaybxyz]

From the Technical content style guidance, it is suggested to use main or develop branch instead of master branch. Also, @barriebyron suggests to add make proto-all guidance in CONTRIBUTING.md doc.