Skip to content

Commit bd56bcd

Browse files
authored
Grammar
1 parent 16b96f6 commit bd56bcd

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

README.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -33,42 +33,42 @@ _____________
3333
- "Textures.def" is a database of known texture hashes
3434
Standardisation
3535
_______________
36-
introduction
36+
Introduction
3737
____________
38-
with a view towards improving file size/general code legibility as well as ensuring that the code all flows together as one; it becomes clear that guidelines need to be created in order to promote these values. please feel free to discuss these choices & make changes as & when needed to ensure that the largest number possible find the code legible & easy to use whilst also performing at its best.
38+
With a view towards improving file size/general code legibility as well as ensuring that the code all flows together as one; it becomes clear that guidelines need to be created in order to promote these values. please feel free to discuss these choices & make changes as & when needed to ensure that the largest number possible find the code legible & easy to use whilst also performing at its best.
3939
__________
40-
sectioning
40+
Sectioning
4141
__________
42-
when doing this please use underscores as they join together, creating a smooth, neat, connected line. ensure they only underline the length of the word & only use them above & below the section header to avoid confusion. done this way a section header need not have an upper gap. each section header should only take up one line, with an additional line above and below for the underscores.
42+
When doing this please use underscores as they join together, creating a smooth, neat, connected line. ensure they only underline the length of the word & only use them above & below the section header to avoid confusion. done this way a section header need not have an upper gap. each section header should only take up one line, with an additional line above and below for the underscores.
4343
___________________
44-
commenting:one line
44+
Commenting:one line
4545
___________________
46-
please comment using "//". using "/*" & "*/" for just one line adds unnecessary extra characters & is easier to break accidentally. do not leave a space before or after the mark used to denote a comment.
46+
Please comment using "//". using "/*" & "*/" for just one line adds unnecessary extra characters & is easier to break accidentally. do not leave a space before or after the mark used to denote a comment.
4747
____________________
48-
commenting:two lines
48+
Commenting:two lines
4949
____________________
50-
please comment "/*" & "*/". using "//" for multiple lines adds unnecessary extra characters. if required, "*" may be used to align text on lines below the topmost line along with a preceding space however only do this if necessary, otherwise do not use any spaces or other such characters for alignment. do not leave spaces around the comment marks.
50+
Please comment "/*" & "*/". using "//" for multiple lines adds unnecessary extra characters. if required, "*" may be used to align text on lines below the topmost line along with a preceding space however only do this if necessary, otherwise do not use any spaces or other such characters for alignment. do not leave spaces around the comment marks.
5151
___________
52-
empty lines
52+
Empty lines
5353
___________
54-
put simply, don't. it is rare that this would even be required.
54+
Put simply, don't. it is rare that this would even be required.
5555
_______
56-
quoting
56+
Quoting
5757
_______
58-
please follow the author's example by using ""
58+
Please follow the author's example by using ""
5959
_____
60-
lists
60+
Lists
6161
_____
62-
please follow the author's example by creating a section header (where applicable) & subsequently preceding each list item with "- ". when unable to use a section header please write a statement ending in ":".
62+
Please follow the author's example by creating a section header (where applicable) & subsequently preceding each list item with "- ". when unable to use a section header please write a statement ending in ":".
6363
______________________
64-
writing the word "and"
64+
Writing the word "and"
6565
______________________
66-
please use "&". if it is required during a quote you may use "and"
66+
Please use "&". if it is required during a quote you may use "and"
6767
______
68-
colons
68+
Colons
6969
______
70-
do not add a space following them.
70+
Do not add a space following them.
7171
__________
72-
signatures
72+
Signatures
7373
__________
74-
please follow the the authors example by preceding a signature with "- "
74+
Please follow the the authors example by preceding a signature with "- "

0 commit comments

Comments
 (0)