docs: fix typos #20734
docs: fix typos #20734
Conversation
WalkthroughWalkthroughThe recent updates focus on semantic refinements and minor textual adjustments across various documentation files, enhancing clarity and grammatical accuracy. No alterations to primary code functionalities or major features are present. Notable changes include corrections in Changes
Sequence Diagram(s) No sequence diagrams are needed for this set of changes as they primarily involve documentation updates without affecting control flow or functionality. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 9
Outside diff range and nitpick comments (7)
README.md (1)
Line range hint
52-52: Consider adding a comma after "design" for better readability.- If you want to follow the updates or learn more about the latest design then join our [Discord](https://discord.gg/interchain). + If you want to follow the updates or learn more about the latest design, then join our [Discord](https://discord.gg/interchain).CONTRIBUTING.md (6)
Line range hint
38-38: Clarify the sentence by adding the missing pronoun.- If want to propose something new that requires specification or an additional design, or you would like to change a process, start with a [new discussion](https://github.com/cosmos/cosmos-sdk/discussions/new). + If you want to propose something new that requires specification or an additional design, or you would like to change a process, start with a [new discussion](https://github.com/cosmos/cosmos-sdk/discussions/new).Tools
LanguageTool
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...If nobody has been assigned to the issue and you would like to work on it, mak...
Line range hint
91-91: Clarify the sentence by using the correct form of "have".- The easiest way to do this is have your editor run it for you upon saving a file + The easiest way to do this is to have your editor run it for you upon saving a fileTools
LanguageTool
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...If nobody has been assigned to the issue and you would like to work on it, mak...
Line range hint
92-92: Clarify the sentence by using the correct verb.- most of the editors will do it anyway using a pre-configured setup of the programming language mode + most of the editors will use it anyway using a pre-configured setup of the programming language modeTools
LanguageTool
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...If nobody has been assigned to the issue and you would like to work on it, mak...
Line range hint
143-148: Consider rewording to avoid repetitive sentence beginnings with "Ensuring".Consider revising the section to vary the sentence structure and avoid repetition.
Tools
LanguageTool
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...If nobody has been assigned to the issue and you would like to work on it, mak...
Line range hint
218-218: Consider using a more specific term instead of "surface level".- If you are only making "surface level" reviews, submit notes as a `comment` review. + If you are only making preliminary reviews, submit notes as a `comment` review.Tools
LanguageTool
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...If nobody has been assigned to the issue and you would like to work on it, mak...
Line range hint
6-303: Adjust the unordered list indentation to comply with Markdownlint rules.- * [Teams Dev Calls](#teams-dev-calls) + * [Teams Dev Calls](#teams-dev-calls) - * [Architecture Decision Records (ADR)](#architecture-decision-records-adr) + * [Architecture Decision Records (ADR)](#architecture-decision-records-adr)Tools
LanguageTool
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...If nobody has been assigned to the issue and you would like to work on it, mak...
Review details
Configuration used: .coderabbit.yml
Review profile: CHILL
Files selected for processing (6)
- CONTRIBUTING.md (2 hunks)
- README.md (1 hunks)
- RELEASES.md (1 hunks)
- RELEASE_PROCESS.md (5 hunks)
- ROADMAP.md (3 hunks)
- UPGRADING.md (3 hunks)
Additional context used
Path-based instructions (6)
RELEASES.md (1)
Pattern
**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"README.md (1)
Pattern
**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"ROADMAP.md (1)
Pattern
**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"RELEASE_PROCESS.md (1)
Pattern
**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"CONTRIBUTING.md (1)
Pattern
**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"UPGRADING.md (1)
Pattern
**/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"
Markdownlint
RELEASES.md
7-7: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spacesROADMAP.md
13-13: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
15-15: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
17-17: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
19-19: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
21-21: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
27-27: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
29-29: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
30-30: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
32-32: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
34-34: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
35-35: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
42-42: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
43-43: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
44-44: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
45-45: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
48-48: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
50-50: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
51-51: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
53-53: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
56-56: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
57-57: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
59-59: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
60-60: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
63-63: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
69-69: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
70-70: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
78-78: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
89-89: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
95-95: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
97-97: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
99-99: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
108-108: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
109-109: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
110-110: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
111-111: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
112-112: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
113-113: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
115-115: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
116-116: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
117-117: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
118-118: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
119-119: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
120-120: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
125-125: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
126-126: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
127-127: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
128-128: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
129-129: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
130-130: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
131-131: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
133-133: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
134-134: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
135-135: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
136-136: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
138-138: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
139-139: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
140-140: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
141-141: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
142-142: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
147-147: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
148-148: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
149-149: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
150-150: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
151-151: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
153-153: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
154-154: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
155-155: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
156-156: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
157-157: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
158-158: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
159-159: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
161-161: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
162-162: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
163-163: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
164-164: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
166-166: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
167-167: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
168-168: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
169-169: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
170-170: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
171-171: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
172-172: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
174-174: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
175-175: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
176-176: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
177-177: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
178-178: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
179-179: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
184-184: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
185-185: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
186-186: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
187-187: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
188-188: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
194-194: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
195-195: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
196-196: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
197-197: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
202-202: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
203-203: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
204-204: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
205-205: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
206-206: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
207-207: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
209-209: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
210-210: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
211-211: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
212-212: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
213-213: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
214-214: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
219-219: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
220-220: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
221-221: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
222-222: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
224-224: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
225-225: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
226-226: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
227-227: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
228-228: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
229-229: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
237-237: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
242-242: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
244-244: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
249-249: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
251-251: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
252-252: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
258-258: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
265-265: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
3-3: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
5-5: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
11-11: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
14-14: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
26-26: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
28-28: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
29-29: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
33-33: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
41-41: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
42-42: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
47-47: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
50-50: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
52-52: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
53-53: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
54-54: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
60-60: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
61-61: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
63-63: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
68-68: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
69-69: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
94-94: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
96-96: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
98-98: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
99-99: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
108-108: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
118-118: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
132-132: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
138-138: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
139-139: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
142-142: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
146-146: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
147-147: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
150-150: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
151-151: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
160-160: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
166-166: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
169-169: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
173-173: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
178-178: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
185-185: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
186-186: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
191-191: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
194-194: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
195-195: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
206-206: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
209-209: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
213-213: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
219-219: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
224-224: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
227-227: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
242-242: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
243-243: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
258-258: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
270-270: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
7-7: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
23-23: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
38-38: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
72-72: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
91-91: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
190-190: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
254-254: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
267-267: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
268-268: Expected: 1; Actual: 3 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
269-269: Expected: 1; Actual: 4 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
75-75: null (MD034, no-bare-urls)
Bare URL used
101-101: null (MD034, no-bare-urls)
Bare URL usedRELEASE_PROCESS.md
18-18: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
19-19: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
20-20: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
21-21: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
22-22: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
24-24: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
25-25: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
27-27: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
28-28: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
29-29: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
30-30: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
32-32: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
33-33: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
34-34: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
35-35: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
36-36: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
37-37: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
39-39: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
40-40: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
41-41: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
42-42: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
44-44: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
45-45: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
46-46: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
47-47: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
69-69: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
126-126: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
127-127: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
129-129: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
131-131: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
132-132: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
133-133: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
135-135: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentationCONTRIBUTING.md
6-6: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
7-7: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
8-8: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
9-9: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
10-10: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
11-11: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
12-12: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
13-13: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
14-14: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
15-15: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
17-17: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
18-18: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
21-21: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
24-24: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
25-25: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
26-26: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
27-27: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
85-85: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
87-87: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
89-89: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
211-211: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
212-212: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
213-213: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
214-214: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
215-215: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
216-216: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
268-268: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
269-269: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
270-270: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
150-150: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
233-233: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
236-236: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
253-253: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
220-220: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
238-238: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines
303-303: null (MD034, no-bare-urls)
Bare URL usedUPGRADING.md
719-719: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
720-720: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
721-721: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
722-722: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
723-723: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
724-724: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
725-725: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
726-726: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
727-727: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
51-51: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
185-185: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
649-649: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
84-84: Column: 1 (MD010, no-hard-tabs)
Hard tabs
85-85: Column: 1 (MD010, no-hard-tabs)
Hard tabs
86-86: Column: 1 (MD010, no-hard-tabs)
Hard tabs
88-88: Column: 1 (MD010, no-hard-tabs)
Hard tabs
89-89: Column: 1 (MD010, no-hard-tabs)
Hard tabs
90-90: Column: 1 (MD010, no-hard-tabs)
Hard tabs
91-91: Column: 1 (MD010, no-hard-tabs)
Hard tabs
93-93: Column: 1 (MD010, no-hard-tabs)
Hard tabs
94-94: Column: 1 (MD010, no-hard-tabs)
Hard tabs
95-95: Column: 1 (MD010, no-hard-tabs)
Hard tabs
96-96: Column: 1 (MD010, no-hard-tabs)
Hard tabs
97-97: Column: 1 (MD010, no-hard-tabs)
Hard tabs
102-102: Column: 1 (MD010, no-hard-tabs)
Hard tabs
103-103: Column: 1 (MD010, no-hard-tabs)
Hard tabs
104-104: Column: 1 (MD010, no-hard-tabs)
Hard tabs
105-105: Column: 1 (MD010, no-hard-tabs)
Hard tabs
106-106: Column: 1 (MD010, no-hard-tabs)
Hard tabs
107-107: Column: 1 (MD010, no-hard-tabs)
Hard tabs
108-108: Column: 1 (MD010, no-hard-tabs)
Hard tabs
110-110: Column: 1 (MD010, no-hard-tabs)
Hard tabs
111-111: Column: 1 (MD010, no-hard-tabs)
Hard tabs
116-116: Column: 1 (MD010, no-hard-tabs)
Hard tabs
117-117: Column: 1 (MD010, no-hard-tabs)
Hard tabs
118-118: Column: 1 (MD010, no-hard-tabs)
Hard tabs
119-119: Column: 1 (MD010, no-hard-tabs)
Hard tabs
120-120: Column: 1 (MD010, no-hard-tabs)
Hard tabs
121-121: Column: 1 (MD010, no-hard-tabs)
Hard tabs
122-122: Column: 1 (MD010, no-hard-tabs)
Hard tabs
123-123: Column: 1 (MD010, no-hard-tabs)
Hard tabs
130-130: Column: 1 (MD010, no-hard-tabs)
Hard tabs
131-131: Column: 1 (MD010, no-hard-tabs)
Hard tabs
132-132: Column: 1 (MD010, no-hard-tabs)
Hard tabs
134-134: Column: 1 (MD010, no-hard-tabs)
Hard tabs
135-135: Column: 1 (MD010, no-hard-tabs)
Hard tabs
136-136: Column: 1 (MD010, no-hard-tabs)
Hard tabs
137-137: Column: 1 (MD010, no-hard-tabs)
Hard tabs
139-139: Column: 1 (MD010, no-hard-tabs)
Hard tabs
140-140: Column: 1 (MD010, no-hard-tabs)
Hard tabs
141-141: Column: 1 (MD010, no-hard-tabs)
Hard tabs
157-157: Column: 1 (MD010, no-hard-tabs)
Hard tabs
162-162: Column: 3 (MD010, no-hard-tabs)
Hard tabs
264-264: Column: 1 (MD010, no-hard-tabs)
Hard tabs
323-323: Column: 3 (MD010, no-hard-tabs)
Hard tabs
324-324: Column: 2 (MD010, no-hard-tabs)
Hard tabs
325-325: Column: 2 (MD010, no-hard-tabs)
Hard tabs
326-326: Column: 2 (MD010, no-hard-tabs)
Hard tabs
327-327: Column: 2 (MD010, no-hard-tabs)
Hard tabs
328-328: Column: 2 (MD010, no-hard-tabs)
Hard tabs
338-338: Column: 1 (MD010, no-hard-tabs)
Hard tabs
339-339: Column: 1 (MD010, no-hard-tabs)
Hard tabs
340-340: Column: 1 (MD010, no-hard-tabs)
Hard tabs
417-417: Column: 2 (MD010, no-hard-tabs)
Hard tabs
420-420: Column: 2 (MD010, no-hard-tabs)
Hard tabs
421-421: Column: 1 (MD010, no-hard-tabs)
Hard tabs
429-429: Column: 2 (MD010, no-hard-tabs)
Hard tabs
433-433: Column: 2 (MD010, no-hard-tabs)
Hard tabs
441-441: Column: 2 (MD010, no-hard-tabs)
Hard tabs
542-542: Column: 1 (MD010, no-hard-tabs)
Hard tabs
543-543: Column: 1 (MD010, no-hard-tabs)
Hard tabs
544-544: Column: 1 (MD010, no-hard-tabs)
Hard tabs
545-545: Column: 1 (MD010, no-hard-tabs)
Hard tabs
546-546: Column: 2 (MD010, no-hard-tabs)
Hard tabs
547-547: Column: 1 (MD010, no-hard-tabs)
Hard tabs
566-566: Column: 1 (MD010, no-hard-tabs)
Hard tabs
567-567: Column: 1 (MD010, no-hard-tabs)
Hard tabs
568-568: Column: 1 (MD010, no-hard-tabs)
Hard tabs
569-569: Column: 1 (MD010, no-hard-tabs)
Hard tabs
570-570: Column: 1 (MD010, no-hard-tabs)
Hard tabs
571-571: Column: 1 (MD010, no-hard-tabs)
Hard tabs
572-572: Column: 1 (MD010, no-hard-tabs)
Hard tabs
573-573: Column: 1 (MD010, no-hard-tabs)
Hard tabs
574-574: Column: 1 (MD010, no-hard-tabs)
Hard tabs
575-575: Column: 1 (MD010, no-hard-tabs)
Hard tabs
586-586: Column: 1 (MD010, no-hard-tabs)
Hard tabs
602-602: Column: 1 (MD010, no-hard-tabs)
Hard tabs
609-609: Column: 1 (MD010, no-hard-tabs)
Hard tabs
638-638: Column: 1 (MD010, no-hard-tabs)
Hard tabs
658-658: Column: 1 (MD010, no-hard-tabs)
Hard tabs
659-659: Column: 1 (MD010, no-hard-tabs)
Hard tabs
660-660: Column: 1 (MD010, no-hard-tabs)
Hard tabs
661-661: Column: 1 (MD010, no-hard-tabs)
Hard tabs
662-662: Column: 1 (MD010, no-hard-tabs)
Hard tabs
663-663: Column: 1 (MD010, no-hard-tabs)
Hard tabs
664-664: Column: 1 (MD010, no-hard-tabs)
Hard tabs
665-665: Column: 1 (MD010, no-hard-tabs)
Hard tabs
666-666: Column: 1 (MD010, no-hard-tabs)
Hard tabs
667-667: Column: 1 (MD010, no-hard-tabs)
Hard tabs
668-668: Column: 1 (MD010, no-hard-tabs)
Hard tabs
669-669: Column: 1 (MD010, no-hard-tabs)
Hard tabs
670-670: Column: 1 (MD010, no-hard-tabs)
Hard tabs
678-678: Column: 1 (MD010, no-hard-tabs)
Hard tabs
679-679: Column: 1 (MD010, no-hard-tabs)
Hard tabs
680-680: Column: 1 (MD010, no-hard-tabs)
Hard tabs
681-681: Column: 1 (MD010, no-hard-tabs)
Hard tabs
682-682: Column: 1 (MD010, no-hard-tabs)
Hard tabs
683-683: Column: 1 (MD010, no-hard-tabs)
Hard tabs
684-684: Column: 1 (MD010, no-hard-tabs)
Hard tabs
685-685: Column: 1 (MD010, no-hard-tabs)
Hard tabs
686-686: Column: 1 (MD010, no-hard-tabs)
Hard tabs
687-687: Column: 1 (MD010, no-hard-tabs)
Hard tabs
688-688: Column: 1 (MD010, no-hard-tabs)
Hard tabs
689-689: Column: 1 (MD010, no-hard-tabs)
Hard tabs
753-753: Column: 1 (MD010, no-hard-tabs)
Hard tabs
754-754: Column: 1 (MD010, no-hard-tabs)
Hard tabs
755-755: Column: 1 (MD010, no-hard-tabs)
Hard tabs
757-757: Column: 1 (MD010, no-hard-tabs)
Hard tabs
758-758: Column: 1 (MD010, no-hard-tabs)
Hard tabs
759-759: Column: 1 (MD010, no-hard-tabs)
Hard tabs
760-760: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1007-1007: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1008-1008: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1009-1009: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1010-1010: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1011-1011: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1035-1035: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1036-1036: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1037-1037: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1059-1059: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1060-1060: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1061-1061: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1062-1062: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1066-1066: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1067-1067: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1068-1068: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1069-1069: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1070-1070: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1071-1071: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1072-1072: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1073-1073: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1074-1074: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1090-1090: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1092-1092: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1093-1093: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1094-1094: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1095-1095: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1096-1096: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1097-1097: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1099-1099: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1101-1101: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1102-1102: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1103-1103: Column: 2 (MD010, no-hard-tabs)
Hard tabs
1115-1115: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1116-1116: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1117-1117: Column: 1 (MD010, no-hard-tabs)
Hard tabs
1191-1191: null (MD037, no-space-in-emphasis)
Spaces inside emphasis markers
1194-1194: null (MD037, no-space-in-emphasis)
Spaces inside emphasis markers
LanguageTool
README.md
[uncategorized] ~52-~52: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... updates or learn more about the latest design then join our [Discord](https://discord...ROADMAP.md
[style] ~5-~5: ‘on a regular basis’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_ON_A_REGULAR_BASIS)
Context: ... This will be a living document updated on a regular basis. If you'd like to participate in any wo...
[typographical] ~5-~5: It seems that a comma is missing. (IF_PLEASE_COMMA)
Context: ...or would like to suggest another feature please reach out to [Marko](mailto:marko@binar...
[style] ~13-~13: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...e. This could entail writing some POC's in order to identify design patterns * [x] Store as...
[uncategorized] ~42-~42: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...on layer similar to the ORM. In the ADR phase it received support from many in the ec...
[grammar] ~60-~60: The word ‘Begin’ is not a noun. Did you mean “beginning” or “start”? (PREPOSITION_VERB)
Context: ...e dependency graph for the future * Begin socializing conventions * [ ] [Remove ...
[grammar] ~96-~96: This phrase is duplicated. You should probably use “migration path” only once. (PHRASE_REPETITION)
Context: ...waiting on reviewers * [x] Prepare the migration path * Migration path has not been finalized * [ ] Test on ma...
[style] ~113-~113: Consider using the more formal “until”. (TILL)
Context: ...udit * Progress: * On pause till ABCI 2.0 ships * [ ] [Optimistic Execut...
[style] ~120-~120: Consider using the more formal “until”. (TILL)
Context: ...ed. * Progress: * On pause till ABCI 2.0 is merged ### Client UX * [ ...
[misspelling] ~148-~148: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’. (EN_A_VS_AN)
Context: ...R. * Objective: * Produce a RFC/ADR on how to make core composable ...
[typographical] ~197-~197: If specifying a range, consider using an en dash instead of a hyphen. (HYPHEN_TO_EN)
Context: ... * Progress: * We have migrated 2-4 modules currently ### Modules * [ ] [...
[grammar] ~222-~222: The name of this brand needs to be capitalized. (ON_SKYPE)
Context: ... * Progress: * Conversations in slack have started * [ ] Cross lang * Obj...
[misspelling] ~228-~228: This word is normally spelled with a hyphen. (EN_COMPOUNDS_BI_WEEKLY)
Context: ...ss: * working group is meeting bi weekly * ADR/RFC is in review ## Q3 ...
[uncategorized] ~270-~270: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...hat was not. Shortly before the quarter concludes a new section will be added for the nex...
[uncategorized] ~270-~270: When a number forms part of an adjectival compound, use a hyphen. (MISSING_HYPHEN)
Context: ...We are working on updating the complete one year roadmap and will be posting it here as ...RELEASE_PROCESS.md
[uncategorized] ~11-~11: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...)_section. Before making a new major release we do beta and release candidate releas...
[grammar] ~26-~26: Possible typo. Did you mean “the” or “All”? (DT_PRP)
Context: ...branch prepare a new version section in theCHANGELOG.md* All links must point to their respective pu...
[uncategorized] ~29-~29: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE_2)
Context: ...d changes in the version. This is needed so the bot knows which entries to add to t...
[uncategorized] ~30-~30: It appears that hyphens are missing in the adjective “up-to-date”. (UP_TO_DATE_HYPHEN)
Context: ... verify that theUPGRADING.mdfile is up to date and contains all the necessary informat...
[uncategorized] ~34-~34: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...sted directly on main. *build.yml: Only the SDK and SimApp need to be buil...
[typographical] ~39-~39: It appears that a comma is missing. (DURING_THAT_TIME_COMMA)
Context: ... in the release branch. * from this point we unfreeze main. * the SDK teams c...
[style] ~40-~40: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...orate and do their best to run testnets in order to validate the release. * when bugs a...
[misspelling] ~57-~57: This word is normally spelled with a hyphen. (EN_COMPOUNDS_CHERRY_PICK)
Context: ...kporting PRs (usually done by automatic cherry pick followed by a PRs to the release branch...
[grammar] ~57-~57: The plural noun “PRs” cannot be used with the article “a”. Did you mean “a PR” or “PRs”? (A_NNS)
Context: ...ne by automatic cherry pick followed by a PRs to the release branch). The backports m...
[style] ~75-~75: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...ease) until they reach End Of Life. Major Release series is maintained in complia...
[uncategorized] ~84-~84: The hyphen in Widely-used is redundant. (ADVERB_LY_HYPHEN_FIX)
Context: ...xes to releases that are not supported. Widely-used (decided at SDK team's discretion) unsu...
[style] ~110-~110: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style. (DIFFERENT_THAN)
Context: ...ements for stable changes are different than those that are candidates to be merged ...
[style] ~111-~111: This phrase might be unnecessarily wordy. (MY_HOPE_IS)
Context: .... When preparing future major releases, our aim is to design the most elegant, user-friend...
[duplication] ~125-~125: Possible typo: you repeated a word (ENGLISH_WORD_REPEAT_RULE)
Context: ...e Release Update (SRU) * High-impact bugs * Bugs that may directly cause a security vuln...
[style] ~153-~153: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...se state corruption or data loss. * Bugs that may directly or indirectly cause a...
[uncategorized] ~159-~159: Possible missing article found. (AI_HYDRA_LEO_MISSING_A)
Context: ...y included in stable point-releases As rule of thumb, the following changes will **...
[uncategorized] ~209-~209: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ...t Release Procedure](CONTRIBUTING.md). Currently residing Stable Release Managers: * @t...
[uncategorized] ~217-~217: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...es The Cosmos SDK repository is a mono-repo where its Go modules have a different r...
[style] ~222-~222: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...ted in an app (e.gx/modules). * Modules that are not imported into an app and a...
[style] ~223-~223: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...andalone module (e.g.cosmovisor). 2. Modules that do not depend on the Cosmos SDK. ...
[uncategorized] ~230-~230: Possible missing preposition found. (AI_HYDRA_LEO_MISSING_OF)
Context: ...same time or soon after a major version Cosmos SDK itself. Those modules can be consid...CONTRIBUTING.md
[uncategorized] ~26-~26: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ...Approval](#concept-approval) * Time Bound Period * [Impl...
[grammar] ~38-~38: It seems that a pronoun is missing. (IF_VB)
Context: ... more appropriate for your needs: 1. If want to propose something new that requ...
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...If nobody has been assigned to the issue and you would like to work on it, mak...
[style] ~51-~51: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase. (EN_WEAK_ADJECTIVE)
Context: ...](#pull-requests) below. Note: For very small or blatantly obvious problems, you are ...
[grammar] ~91-~91: Consider using either the past participle “had” or the present participle “having” here. (BEEN_PART_AGREEMENT)
Context: ...commit. The easiest way to do this is have your editor run it for you upon saving ...
[grammar] ~92-~92: Did you mean “use”? (DO_PRP_RB_VBG)
Context: ...most of the editors will do it anyway using a pre-configured setup of the programmi...
[uncategorized] ~113-~113: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...s good to have early validation of your work and we highly recommend this practice. ...
[uncategorized] ~117-~117: “Other things” (plural) doesn’t require “other” to be in plural. (OTHERS)
Context: ...mat). The entry should be on top of all others changes in the section. PRs must have a catego...
[grammar] ~119-~119: In this context, ‘type’ should agree in number with the noun after ‘of’. (TYPE_OF_PLURAL)
Context: ... a category prefix that is based on the type of changes being made (for example,fix,feat,...
[uncategorized] ~141-~141: It appears that hyphens are missing in the adjective “up-to-date”. (UP_TO_DATE_HYPHEN)
Context: ...is includes: * Ensuring that the PR is up to date with the latest changes in the main bra...
[style] ~143-~143: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...suring that the PR passes all checks. * Ensuring that the PR has a clear description of ...
[style] ~144-~144: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...s a clear description of the changes. * Ensuring that the PR has a clear description of ...
[style] ~145-~145: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ... description of the testing strategy. * Ensuring that the PR has a clear description of ...
[style] ~146-~146: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...ription of the impact of the changes. * Ensuring that the PR has a clear description of ...
[style] ~147-~147: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...he risks associated with the changes. * Ensuring that the PR has a clear description of ...
[style] ~148-~148: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ... clear description of the next steps. * Ensuring that the PR has a clear description of ...
[uncategorized] ~150-~150: The preposition ‘to’ seems more likely in this position. (AI_HYDRA_LEO_REPLACE_ON_TO)
Context: ... is responsible for assigning reviewers on the team, responding to feedback, and e...
[uncategorized] ~150-~150: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ed, but an approval is not given by the reviewer the pull request owner is responsible f...
[style] ~192-~192: Unless you want to emphasize “not”, use “cannot” which is more common. (CAN_NOT_PREMIUM)
Context: ...nal Contributors External contributors can not manage getting reviewers and assigning ...
[style] ~195-~195: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...oving forward. ### Requesting Reviews In order to accommodate the review process, the aut...
[style] ~218-~218: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...n theApprovalor your PR comments. * If you are only making "surface level" rev...
[style] ~218-~218: ‘surface level’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_SURFACE_LEVEL)
Context: ... PR comments. * If you are only making "surface level" reviews, submit notes as acommentr...
[style] ~226-~226: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: .../ordocs/building-modules/folders. * If your changes relate to the core of the ...
[uncategorized] ~226-~226: Possible missing article found. (AI_HYDRA_LEO_MISSING_THE)
Context: ...he core of the CLI (not specifically to module's CLI/Rest), then modify the content in...
[style] ~227-~227: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE)
Context: ...ntent in thedocs/run-node/folder. * If your changes relate to a module, then b...
[uncategorized] ~303-~303: This expression is usually spelled with a hyphen. (BASED_HYPHEN)
Context: ... User-facing repos should adhere to the trunk based development branching model: https://tr...
[style] ~303-~303: It’s more common nowadays to write this noun as one word. (RECOMMENDED_COMPOUNDS)
Context: ....com. User branches should start with a user name, example: `{moniker}/{issue#}-branch-na...
[grammar] ~340-~340: Because the auxiliary verb ‘have’ is already present, the ‘had’ in ‘had acted’ may be superfluous here. (MULTIPLE_PARTICIPLE)
Context: ... is demonstrably shown to intentionally have had acted maliciously or grossly negligent, code-...
[uncategorized] ~348-~348: Possible missing preposition found. (AI_HYDRA_LEO_MISSING_IN)
Context: ...mber should be removed / replaced * Violation of Code of Conduct Earning this privil...
[uncategorized] ~362-~362: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ...al** ### Strategy Discovery * Develop long term priorities, strategy and roadmap for th...
[style] ~363-~363: This phrasing can be wordy. For improved clarity, try opting for something more concise. (FOR_THE_TIME_BEING)
Context: ...e is already a roadmap that can be used for the time being ### Concept Approval * Architecture D...
[uncategorized] ~370-~370: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ...tecture/PROCESS.md) * After proposal, a time bound period for Request for Comment (RFC) on...
[uncategorized] ~373-~373: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ...hile still in aProposedstatus #### Time Bound Period * Once a PR for an ADR is opene...
[uncategorized] ~376-~376: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ...hin 1 week of pull request being open * Time bound period for individual ADR Pull Requests...
[uncategorized] ~377-~377: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ...erged should not exceed 2 weeks * Total time bound period for an ADR to reach a decision (...
[style] ~383-~383: ‘final conclusion’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_FINAL_CONCLUSION)
Context: ...s taking longer than 4 weeks to reach a final conclusion, there should be a synchronous meeting ...
[grammar] ~383-~383: This noun is normally spelled as one word. (HOLDER_COMPOUNDS)
Context: ...chronous meeting with reviewers and all stake holders * unanimously setting a new time bound...
[uncategorized] ~385-~385: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ...ke holders * unanimously setting a new time bound period for this ADR * making changes to...
[style] ~386-~386: Consider shortening or rephrasing this to strengthen your wording. (MAKE_CHANGES)
Context: ... a new time bound period for this ADR * making changes to the Concept Approval Process (as outlin...
[style] ~387-~387: Consider shortening or rephrasing this to strengthen your wording. (MAKE_CHANGES)
Context: ...t Approval Process (as outlined here) * making changes to the members of the Concept Approval Com...
[grammar] ~391-~391: Probable usage error. Use “and” after ‘both’. (BOTH_AS_WELL_AS)
Context: ...plementation PRs corresponding to ADRs, as well as for PRs made as part of a release proce...UPGRADING.md
[typographical] ~10-~10: It appears that a comma is missing. (DURING_THAT_TIME_COMMA)
Context: .... ## [Unreleased] ### SimApp In this section we describe the changes made in Cosmos ...
[uncategorized] ~126-~126: Possible missing article found. (AI_HYDRA_LEO_MISSING_A)
Context: ...sures the manager's state is written to file such that when the node restarts, it ...
[grammar] ~171-~171: The verb ‘depend’ can be stative. If ‘depending’ describes a state, change the sentence structure and use the base form of the verb. (PROGRESSIVE_VERBS)
Context: ...ild/docs/bsr/generated-sdks/go). If you were depending oncosmossdk.io/api/tendermint, pleas...
[grammar] ~181-~181: The verb ‘recommend’ is used with the gerund form. (ADMIT_ENJOY_VB)
Context: ...precation ofsdk.Context, we strongly recommend to use thecosmossdk.io/core/appmoduleinter...
[uncategorized] ~225-~225: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... (sdk.Msg, error) ``` ##### Depinject Previouslycosmossdk.io/coreheld functions `Inv...
[style] ~231-~231: ‘prior to’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_PRIOR_TO)
Context: ...ved. It is required to migrate to v0.50 prior to upgrading to v0.51 for not missing any ...
[grammar] ~252-~252: The singular determiner ‘this’ may not agree with the plural noun ‘changes’. Did you mean “these”? (THIS_NNS)
Context: ...Many functions have been removed due to this changes as the API can be smaller thank...
[uncategorized] ~257-~257: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...will be used as a global account number tracking replacing Auth legacy AccountNumber. Mu...
[uncategorized] ~277-~277: Possible missing article found. (AI_HYDRA_LEO_MISSING_THE)
Context: ...cosmossdk.io/x/authz####x/bankBank was spun out into its owngo.mod. To ...
[uncategorized] ~287-~287: Possible missing article found. (AI_HYDRA_LEO_MISSING_THE)
Context: ...x/protocolpool module. ####x/groupGroup was spun out into its owngo.mod. To ...
[uncategorized] ~313-~313: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...ams` A standalone Go module was created and it is accessible at "cosmossdk.io/x/par...
[typographical] ~381-~381: It appears that a comma is missing. (BY_FOR_IN_COMMA)
Context: ...genesis.json` file. For existing chains this can be done in two ways: * During an u...
[typographical] ~383-~383: Consider adding a comma after this introductory phrase. (AS_A_NN_COMMA)
Context: ...s can be done in two ways: * During an upgrade the value is set in an upgrade handler....
[uncategorized] ~390-~390: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE_2)
Context: ...here a catastrophic failure has occurred and the application should halt. However, t...
[misspelling] ~392-~392: Did you maybe mean “buy” or “be”? (BY_BUY)
Context: ... that returns an error, will gracefully by handled byBaseAppon behalf of the a...
[style] ~397-~397: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...lizeBlock` is public and should be used in order to test and run operations. This means tha...
[grammar] ~410-~410: Did you mean “modifying”? Or maybe you should add a pronoun? In active voice, ‘allow’ + ‘to’ takes an object, usually a pronoun. (ALLOW_TO)
Context: ...begin blocker other modules, and allows to modify consensus parameters, and the changes a...
[uncategorized] ~448-~448: A comma may be missing after the conjunctive/linking adverb ‘Instead’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ...he case of successful msg(s) execution. Instead a new attribute is added to all message...
[grammar] ~475-~475: The word “clean-up” is a noun. The verb is spelled with a white space. (NOUN_VERB_CONFUSION)
Context: ...s well as its settings. Useconfixto clean-up yourapp.toml. A nginx (or alike) rev...
[typographical] ~479-~479: Consider adding a comma here. (PLEASE_COMMA)
Context: ...pported database to a supported database please use a database migration tool. ### Pro...
[typographical] ~496-~496: It appears that a comma is missing. (DURING_THAT_TIME_COMMA)
Context: ...tate-machine code. ### SimApp In this section we describe the changes made in Cosmos ...
[uncategorized] ~560-~560: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE_2)
Context: ...on. The global variable has been removed and the basic module manager can be now cre...
[uncategorized] ~596-~596: A comma may be missing after the conjunctive/linking adverb ‘Additionally’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... not to be included in the binary. ::: AdditionallyAutoCLIautomatically adds the custom...
[uncategorized] ~627-~627: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... is extracted to have a separate go.mod file which allows it be a standalone module....
[grammar] ~627-~627: The preposition ‘to’ may be missing (allow someone to do something). (ALLOW_TO_DO)
Context: ... a separate go.mod file which allows it be a standalone module. All the store impo...
[misspelling] ~648-~648: This word is normally spelled with a hyphen. (EN_COMPOUNDS_HUMAN_READABLE)
Context: ...available in the SDK that produces more human readable output, currently only available on Led...
[grammar] ~692-~692: Two determiners in a row. Choose either “the” or “a”. (DT_DT)
Context: ...``` When usingdepinject/ `app v2`, the a tx config should be recreated from the ...
[grammar] ~717-~717: It looks like ‘interfaces’ doesn’t match ‘an’. Did you mean “an interface” or just “interfaces”? (A_NNS_IN)
Context: ...d ofsdk.Context. Any module that has an interfaces for them (like "expected keepers") will...
[uncategorized] ~741-~741: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...EndBlock(context.Context) error ``` In case a module requires to return `abci.Valid...
[uncategorized] ~768-~768: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ge. The signer field is required on all messages unless using a custom signer function. ...
[typographical] ~770-~770: Consider adding a comma here. (PLEASE_COMMA)
Context: ...ustom signer function. To find out more please read the [signer field](https://github....
[misspelling] ~783-~783: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’. (EN_A_VS_AN)
Context: ...has migrated from a CometBFT genesis to a application managed genesis file. The g...
[misspelling] ~803-~803: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’. (EN_A_VS_AN)
Context: ...ameter. An expedited proposal must have an higher voting threshold than a classic ...
[uncategorized] ~807-~807: It seems likely that a singular genitive (’s) apostrophe is missing. (AI_HYDRA_LEO_APOSTROPHE_S_XS)
Context: ...nt toProposalCancelDestaddress. The deposits burn rate will be determined by a new p...
[uncategorized] ~820-~820: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... is extracted to have a separate go.mod file which allows it be a standalone module....
[grammar] ~820-~820: The preposition ‘to’ may be missing (allow someone to do something). (ALLOW_TO_DO)
Context: ... a separate go.mod file which allows it be a standalone module. All the evidence i...
[uncategorized] ~827-~827: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... is extracted to have a separate go.mod file which allows it to be a standalone modu...
[uncategorized] ~834-~834: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... is extracted to have a separate go.mod file which allows it to be a standalone modu...
[uncategorized] ~841-~841: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... is extracted to have a separate go.mod file which allows it to be a standalone modu...
[grammar] ~848-~848: Did you mean the possessive pronoun “its”? (IT_S_ITS)
Context: ...ing #### Rosetta Rosetta has moved to it's own [repo](https://github.com/cosmos/ro...
[uncategorized] ~849-~849: After the verb ‘interested’ the preposition “in” is used. (CONFUSION_OF_INTERESTED_ON_IN)
Context: ... by default. Any user who is interested on using the tool can connect it standalon...
[misspelling] ~850-~850: This word is normally spelled as one. (EN_COMPOUNDS_MULTI_CHAIN)
Context: ...de binary. The rosetta tool also allows multi chain connections. ## [v0.47.x](https://gith...
[typographical] ~872-~872: The word “however” is an adverb that can’t be used like a conjunction, and therefore needs to be separated from the sentence. (HOWEVER_SENTENCE)
Context: ...dom parameter changes during simulations, however, it does so through ParamChangeProposal ...
[grammar] ~874-~874: The noun should probably be in the singular form. (EVERY_EACH_SINGULAR)
Context: ...teParamsgovernance proposals for each modules,AppModuleSimulationnow defines aA...
[style] ~889-~889: Consider using “formerly” to strengthen your wording. (PREVIOUSLY_FORMERLY)
Context: ... modules no longer support the REST API previously known as the LCD, and the `sdk.Msg#Rout...
[style] ~906-~906: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...dd the following lines to yourapp.goin order to provide newer gRPC services: ```go aut...
[uncategorized] ~923-~923: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...riod). These were unnecessary given as arguments as they were already present in theAp...
[uncategorized] ~927-~927: A comma may be missing after the conjunctive/linking adverb ‘Instead’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ...)was deprecated and has been removed. Instead you can use theTestEncodingConfig` fr...
[grammar] ~937-~937: The modal verb ‘must’ requires the verb’s base form. (MD_BASEFORM)
Context: ... Replaces TheGoLevelDBversion must pinned to `v1.0.1-0.20210819022825-2ae1ddf74ef...
[grammar] ~948-~948: The word ‘replace’ is a verb. Did you mean the noun “replacement”? (PREPOSITION_VERB)
Context: ...goproto. This allows you to remove the replace directivereplace github.com/gogo/prot...
[formatting] ~956-~956: You have used ‘I’ with an apostrophe, but either the verb is missing or you have not used the corresponding abbreviated form. Consider using one of the suggestions or removing the apostrophe. (I_APOSTROPHE_X)
Context: ...ly the rootproto/folder, set by theprotoc -Iflag). For example, assuming you put a...
[style] ~966-~966: Although a hyphen is possible, it is not necessary in a compound modifier in which the first word is an adverb that ends in ‘ly’. (HYPHENATED_LY_ADVERB_ADJECTIVE)
Context: ...ace` annotations. We require them to be fully-scoped names. They will soon be used by code g...
[style] ~984-~984: The word “also” tends to be overused. Consider using a formal alternative to strengthen your wording. (PLEASE_ALSO_CHECK)
Context: ...os.feegrant.v1beta1.FeeAllowanceI" ``` Please also check that in your own app's proto file...
[style] ~985-~985: Try using a more formal synonym for ‘check’. (VERIFY)
Context: ...v1beta1.FeeAllowanceI" ``` Please also check that in your own app's proto files that...
[style] ~985-~985: Although a hyphen is possible, it is not necessary in a compound modifier in which the first word is an adverb that ends in ‘ly’. (HYPHENATED_LY_ADVERB_ADJECTIVE)
Context: ...otations. If so, then replace them with fully-qualified names, even though those names don't ac...
[locale-violation] ~1025-~1025: In American English, “take a look” is more commonly used. (HAVE_A_LOOK)
Context: ...e modules keepers in previous versions. Have a look atsimapp.RegisterUpgradeHandlers()f...
[misspelling] ~1043-~1043: Did you mean “At a Time”, “At the Time”, or “At times”? (AT_TIME2)
Context: ...x/gov##### Minimum Proposal Deposit At Time of Submission Thegovmodule has bee...
[misspelling] ~1050-~1050: Did you mean “at a time”, “at the time”, or “at times”? (AT_TIME2)
Context: ...o utilize the minimum proposal deposits at time of submission, the migration logic need...
[uncategorized] ~1082-~1082: A comma is probably missing here. (MISSING_COMMA_AFTER_INTRODUCTORY_PHRASE)
Context: ...ng Tendermint consensus parameters. For migration it is required to call a specific migra...
[style] ~1109-~1109: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...should still be imported in your app.go in order to handle this migration. Because the `x/...
[style] ~1171-~1171: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...ally, new packages have been introduced in order to further split the codebase. Aliases are...
[uncategorized] ~1203-~1203: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ndex represents the latest state of the IAVL laid out in a format that preserves dat...
[uncategorized] ~1222-~1222: Possible missing article found. (AI_HYDRA_LEO_MISSING_A)
Context: ...ur of each module housing and providing way to modify their parameters. Each module...
[typographical] ~1223-~1223: It appears that a comma is missing. (DURING_THAT_TIME_COMMA)
Context: ...aintained until April 18, 2023. At this point the module will reach end of life and b...
[style] ~1228-~1228: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...the new implementation is calledv1. In order to submit a proposal with `submit-proposal...
[style] ~1235-~1235: ‘by accident’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_BY_ACCIDENT)
Context: ...g delegations. Users that have unbonded by accident or wish to cancel an undelegation can n...
[style] ~1241-~1241: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...build/cosmos/cosmos-sdk` as dependency, in order to avoid having to copy paste these files....
[grammar] ~1241-~1241: Did you mean “copy and paste”? (COPY_PASTE)
Context: ...dependency, in order to avoid having to copy paste these files. The protos can as well be...
[uncategorized] ~1259-~1259: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ..."]; } ``` When clients interact with a node they are required to set a codec in in ...
[duplication] ~1259-~1259: Possible typo: you repeated a word (ENGLISH_WORD_REPEAT_RULE)
Context: ...a node they are required to set a codec in in the grpc.Dial. More information can be ...
Additional comments not posted (6)
RELEASES.md (1)
3-3: Remove trailing spaces for markdown consistency.- The Cosmos-SDK follows both [0ver](https://0ver.org/) and [Semver](https://semver.org/). While this is confusing let's break it down: 0ver is used for the main Cosmos-SDK dependency (`github.com/cosmos/cosmos-sdk`) and Semver is used for all other dependencies. + The Cosmos-SDK follows both [0ver](https://0ver.org/) and [Semver](https://semver.org/). While this is confusing let's break it down: 0ver is used for the main Cosmos-SDK dependency (`github.com/cosmos/cosmos-sdk`) and Semver is used for all other dependencies.Likely invalid or redundant comment.
README.md (1)
81-81: Corrected grammar from "a application" to "an application" improves readability and professionalism.ROADMAP.md (3)
203-203: This change introduces a new system for checking invariants, which is crucial for maintaining the integrity of the system.Tools
Markdownlint
203-203: Expected: 4; Actual: 8 (MD007, ul-indent)
Unordered list indentation
48-48: The addition of "sign mode textual" to the roadmap provides clarity on the development focus and timelines.Tools
Markdownlint
48-48: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
69-69: The integration testing framework is a significant addition, enhancing module dependency management.Tools
Markdownlint
69-69: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
69-69: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spacesRELEASE_PROCESS.md (1)
23-23: Ensure consistency in the protection rules for the release branch.
| @@ -66,7 +66,7 @@ After the release branch has all commits required for the next patch release: | |||
|
|
|||
| * Update `CHANGELOG.md` and `RELEASE_NOTES.md` (if applicable). | |||
| * Create a new annotated git tag (eg `git -a v1.1.0`) in the release branch. | |||
| * If the release is a submodule update, first go the submodule folder and name the tag prepending the path to the version: | |||
| * If the release is a submodule update, first go to the submodule folder and name the tag prepending the path to the version: | |||
There was a problem hiding this comment.
Improve clarity in submodule tagging instructions.
Consider providing examples or more detailed steps for tagging submodules, especially for those unfamiliar with the process.
Tools
Markdownlint
69-69: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
| @@ -31,7 +31,7 @@ | |||
| * Remove GitHub workflows that should not be in the release branch | |||
| * `test.yml`: All standalone go module tests should be removed (expect `./simapp`, and `./tests`, SDK and modules tests). | |||
| * These packages are tracked and tested directly on main. | |||
| * `build.yml`: Only the SDK and SimApp needs to be built on release branches. | |||
| * `build.yml`: Only the SDK and SimApp need to be built on release branches. | |||
There was a problem hiding this comment.
Clarify the exclusion of tooling from the build process on release branches.
It's mentioned that tooling depending on the SDK needs to be built, but it's unclear which specific tools this includes. Can you clarify this in the documentation?
Tools
LanguageTool
[uncategorized] ~34-~34: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...sted directly on main. *build.yml: Only the SDK and SimApp need to be buil...
Markdownlint
34-34: Expected: 2; Actual: 4 (MD007, ul-indent)
Unordered list indentation
| @@ -43,7 +43,7 @@ contributors, the general procedure for contributing has been established: | |||
| 1. Ensure that the proposal has been accepted. | |||
| 2. Ensure that nobody else has already begun working on this issue. If they have, | |||
| make sure to contact them to collaborate. | |||
| 3. If nobody has been assigned for the issue and you would like to work on it, | |||
| 3. If nobody has been assigned to the issue and you would like to work on it, | |||
There was a problem hiding this comment.
Consider adding a comma after "issue" for better readability.
- If nobody has been assigned to the issue and you would like to work on it,
+ If nobody has been assigned to the issue, and you would like to work on it,Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| 3. If nobody has been assigned to the issue and you would like to work on it, | |
| 3. If nobody has been assigned to the issue, and you would like to work on it, |
Tools
LanguageTool
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...If nobody has been assigned to the issue and you would like to work on it, mak...
| @@ -1219,7 +1219,7 @@ mistakes. | |||
|
|
|||
| #### `x/params` | |||
|
|
|||
| * The `x/params` module has been deprecated in favour of each module housing and providing way to modify their parameters. Each module that has parameters that are changeable during runtime have an authority, the authority can be a module or user account. The Cosmos SDK team recommends migrating modules away from using the param module. An example of how this could look like can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363). | |||
| * The `x/params` module has been deprecated in favour of each module housing and providing way to modify their parameters. Each module that has parameters that are changeable during runtime has an authority, the authority can be a module or user account. The Cosmos SDK team recommends migrating modules away from using the param module. An example of how this could look like can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363). | |||
| * The Param module will be maintained until April 18, 2023. At this point the module will reach end of life and be removed from the Cosmos SDK. | |||
There was a problem hiding this comment.
Add a comma for grammatical correctness.
- The Param module will be maintained until April 18, 2023. At this point the module will reach end of life and be removed from the Cosmos SDK.
+ The Param module will be maintained until April 18, 2023. At this point, the module will reach end of life and be removed from the Cosmos SDK.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| * The Param module will be maintained until April 18, 2023. At this point the module will reach end of life and be removed from the Cosmos SDK. | |
| * The Param module will be maintained until April 18, 2023. At this point, the module will reach end of life and be removed from the Cosmos SDK. |
Tools
LanguageTool
[typographical] ~1223-~1223: It appears that a comma is missing. (DURING_THAT_TIME_COMMA)
Context: ...aintained until April 18, 2023. At this point the module will reach end of life and b...
|
|
||
| ### Protobuf | ||
|
|
||
| The `third_party/proto` folder that existed in [previous version](https://github.com/cosmos/cosmos-sdk/tree/v0.45.3/third_party/proto) now does not contains directly the [proto files](https://github.com/cosmos/cosmos-sdk/tree/release/v0.46.x/third_party/proto). | ||
| The `third_party/proto` folder that existed in [previous version](https://github.com/cosmos/cosmos-sdk/tree/v0.45.3/third_party/proto) now does not contain directly the [proto files](https://github.com/cosmos/cosmos-sdk/tree/release/v0.46.x/third_party/proto). |
There was a problem hiding this comment.
Correct the file path formatting for consistency and clarity.
- The `third_party/proto` folder that existed in [previous version](https://github.com/cosmos/cosmos-sdk/tree/v0.45.3/third_party/proto) now does not contain directly the [proto files](https://github.com/cosmos/cosmos-sdk/tree/release/v0.46.x/third_party/proto).
+ The `third_party/proto` folder that existed in the [previous version](https://github.com/cosmos/cosmos-sdk/tree/v0.45.3/third_party/proto) no longer directly contains the [proto files](https://github.com/cosmos/cosmos-sdk/tree/release/v0.46.x/third_party/proto).Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| The `third_party/proto` folder that existed in [previous version](https://github.com/cosmos/cosmos-sdk/tree/v0.45.3/third_party/proto) now does not contain directly the [proto files](https://github.com/cosmos/cosmos-sdk/tree/release/v0.46.x/third_party/proto). | |
| The `third_party/proto` folder that existed in the [previous version](https://github.com/cosmos/cosmos-sdk/tree/v0.45.3/third_party/proto) no longer directly contains the [proto files](https://github.com/cosmos/cosmos-sdk/tree/release/v0.46.x/third_party/proto). |
| @@ -1232,11 +1232,11 @@ | |||
|
|
|||
| #### `x/staking` | |||
|
|
|||
| The `staking module` added a new message type to cancel unbonding delegations. Users that have unbonded by accident or wish to cancel a undelegation can now specify the amount and valdiator they would like to cancel the unbond from | |||
| The `staking module` added a new message type to cancel unbonding delegations. Users that have unbonded by accident or wish to cancel an undelegation can now specify the amount and validator they would like to cancel the unbond from | |||
There was a problem hiding this comment.
Clarify the action in the sentence for better readability.
- The `staking module` added a new message type to cancel unbonding delegations. Users that have unbonded by accident or wish to cancel an undelegation can now specify the amount and validator they would like to cancel the unbond from
+ The `staking module` has added a new message type to cancel unbonding delegations. Users who have unbonded by accident or wish to cancel an undelegation can now specify the amount and validator from which they would like to cancel the unbonding.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| The `staking module` added a new message type to cancel unbonding delegations. Users that have unbonded by accident or wish to cancel an undelegation can now specify the amount and validator they would like to cancel the unbond from | |
| The `staking module` has added a new message type to cancel unbonding delegations. Users who have unbonded by accident or wish to cancel an undelegation can now specify the amount and validator from which they would like to cancel the unbonding. |
Tools
LanguageTool
[style] ~1235-~1235: ‘by accident’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_BY_ACCIDENT)
Context: ...g delegations. Users that have unbonded by accident or wish to cancel an undelegation can n...
| @@ -476,7 +476,7 @@ | |||
|
|
|||
| #### Database Support | |||
|
|
|||
| ClevelDB, BoltDB and BadgerDB are not supported anymore. To migrate from a unsupported database to a supported database please use a database migration tool. | |||
| ClevelDB, BoltDB and BadgerDB are not supported anymore. To migrate from an unsupported database to a supported database please use a database migration tool. | |||
There was a problem hiding this comment.
Consider adding a comma after "database" for clarity.
- ClevelDB, BoltDB and BadgerDB are not supported anymore. To migrate from an unsupported database to a supported database please use a database migration tool.
+ ClevelDB, BoltDB and BadgerDB are not supported anymore. To migrate from an unsupported database to a supported database, please use a database migration tool.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ClevelDB, BoltDB and BadgerDB are not supported anymore. To migrate from an unsupported database to a supported database please use a database migration tool. | |
| ClevelDB, BoltDB and BadgerDB are not supported anymore. To migrate from an unsupported database to a supported database, please use a database migration tool. |
Tools
LanguageTool
[typographical] ~479-~479: Consider adding a comma here. (PLEASE_COMMA)
Context: ...pported database to a supported database please use a database migration tool. ### Pro...
| @@ -1219,7 +1219,7 @@ | |||
|
|
|||
| #### `x/params` | |||
|
|
|||
| * The `x/params` module has been deprecated in favour of each module housing and providing way to modify their parameters. Each module that has parameters that are changeable during runtime have an authority, the authority can be a module or user account. The Cosmos SDK team recommends migrating modules away from using the param module. An example of how this could look like can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363). | |||
| * The `x/params` module has been deprecated in favour of each module housing and providing way to modify their parameters. Each module that has parameters that are changeable during runtime has an authority, the authority can be a module or user account. The Cosmos SDK team recommends migrating modules away from using the param module. An example of how this could look like can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363). | |||
There was a problem hiding this comment.
Consider rephrasing for grammatical accuracy and clarity.
- * The `x/params` module has been deprecated in favour of each module housing and providing way to modify their parameters. Each module that has parameters that are changeable during runtime has an authority, the authority can be a module or user account. The Cosmos SDK team recommends migrating modules away from using the param module. An example of how this could look like can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363).
+ * The `x/params` module has been deprecated in favour of each module housing and providing a way to modify their parameters. Each module that has parameters changeable during runtime has an authority, which can be a module or a user account. The Cosmos SDK team recommends migrating modules away from using the param module. An example of how this can be done can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363).Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| * The `x/params` module has been deprecated in favour of each module housing and providing way to modify their parameters. Each module that has parameters that are changeable during runtime has an authority, the authority can be a module or user account. The Cosmos SDK team recommends migrating modules away from using the param module. An example of how this could look like can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363). | |
| * The `x/params` module has been deprecated in favour of each module housing and providing a way to modify their parameters. Each module that has parameters changeable during runtime has an authority, which can be a module or a user account. The Cosmos SDK team recommends migrating modules away from using the param module. An example of how this can be done can be found [here](https://github.com/cosmos/cosmos-sdk/pull/12363). |
Tools
LanguageTool
[uncategorized] ~1222-~1222: Possible missing article found. (AI_HYDRA_LEO_MISSING_A)
Context: ...ur of each module housing and providing way to modify their parameters. Each module...
|
|
||
| ## Semver Dependencies | ||
|
|
||
| Although we adhere to semantic versioning (semver), we have introduced a few modifications to accommodate the unique characteristics of blockchains. One significant divergence is that the major version (Y.x.x) is incremented solely when a consensus-breaking change occurs. On the other hand, the minor version (x.Y.x) is increased when there is a non-consensus-breaking alteration that also results in an incompatible API change. Patch versions will be bumped for all other changes that dont break the API nor Consensus. | ||
| Although we adhere to semantic versioning (semver), we have introduced a few modifications to accommodate the unique characteristics of blockchains. One significant divergence is that the major version (Y.x.x) is incremented solely when a consensus-breaking change occurs. On the other hand, the minor version (x.Y.x) is increased when there is a non-consensus-breaking alteration that also results in an incompatible API change. Patch versions will be bumped for all other changes that don't break the API nor Consensus. |
There was a problem hiding this comment.
Remove trailing spaces to adhere to markdown best practices.
- Although we adhere to semantic versioning (semver), we have introduced a few modifications to accommodate the unique characteristics of blockchains. One significant divergence is that the major version (Y.x.x) is incremented solely when a consensus-breaking change occurs. On the other hand, the minor version (x.Y.x) is increased when there is a non-consensus-breaking alteration that also results in an incompatible API change. Patch versions will be bumped for all other changes that don't break the API nor Consensus.
+ Although we adhere to semantic versioning (semver), we have introduced a few modifications to accommodate the unique characteristics of blockchains. One significant divergence is that the major version (Y.x.x) is incremented solely when a consensus-breaking change occurs. On the other hand, the minor version (x.Y.x) is increased when there is a non-consensus-breaking alteration that also results in an incompatible API change. Patch versions will be bumped for all other changes that don't break the API nor Consensus.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Although we adhere to semantic versioning (semver), we have introduced a few modifications to accommodate the unique characteristics of blockchains. One significant divergence is that the major version (Y.x.x) is incremented solely when a consensus-breaking change occurs. On the other hand, the minor version (x.Y.x) is increased when there is a non-consensus-breaking alteration that also results in an incompatible API change. Patch versions will be bumped for all other changes that don't break the API nor Consensus. | |
| Although we adhere to semantic versioning (semver), we have introduced a few modifications to accommodate the unique characteristics of blockchains. One significant divergence is that the major version (Y.x.x) is incremented solely when a consensus-breaking change occurs. On the other hand, the minor version (x.Y.x) is increased when there is a non-consensus-breaking alteration that also results in an incompatible API change. Patch versions will be bumped for all other changes that don't break the API nor Consensus. |
Tools
Markdownlint
7-7: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces
docs: fix typos
Summary by CodeRabbit
Documentation
README.md,CONTRIBUTING.md,ROADMAP.md,UPGRADING.md, andRELEASES.md.RELEASES.md.RELEASE_PROCESS.md.New Features
x/stakingmodule to cancel unbonding delegations.Deprecations
x/paramsmodule, suggesting migration to individual modules managing their parameters.