Skip to content

Commit 4e3a6f2

Browse files
authored
Correct grammar for NR.2 (#2228)
1 parent 48c3395 commit 4e3a6f2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

CppCoreGuidelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20583,7 +20583,7 @@ The positive arguments for alternatives to these non-rules are listed in the rul
2058320583
Non-rule summary:
2058420584

2058520585
* [NR.1: Don't insist that all declarations should be at the top of a function](#Rnr-top)
20586-
* [NR.2: Don't insist to have only a single `return`-statement in a function](#Rnr-single-return)
20586+
* [NR.2: Don't insist on having only a single `return`-statement in a function](#Rnr-single-return)
2058720587
* [NR.3: Don't avoid exceptions](#Rnr-no-exceptions)
2058820588
* [NR.4: Don't insist on placing each class definition in its own source file](#Rnr-lots-of-files)
2058920589
* [NR.5: Don't use two-phase initialization](#Rnr-two-phase-init)
@@ -20629,7 +20629,7 @@ Unfortunately, compilers cannot catch all such errors and unfortunately, the bug
2062920629
* [Always initialize an object](#Res-always)
2063020630
* [ES.21: Don't introduce a variable (or constant) before you need to use it](#Res-introduce)
2063120631

20632-
### <a name="Rnr-single-return"></a>NR.2: Don't insist to have only a single `return`-statement in a function
20632+
### <a name="Rnr-single-return"></a>NR.2: Don't insist on having only a single `return`-statement in a function
2063320633

2063420634
##### Reason
2063520635

0 commit comments

Comments
 (0)