Skip to content

Commit c8a5418

Browse files
committed
Remove trailing spaces and extra blank lines
1 parent 75caa18 commit c8a5418

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

docs/query-help-style-guide.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ When you contribute a new [supported query](supported-queries.md) to this reposi
1616

1717
### Location and file name
1818

19-
Query help files must have the same base name as the query they describe and must be located in the same directory.
19+
Query help files must have the same base name as the query they describe and must be located in the same directory.
2020

2121
### File structure and layout
2222

@@ -42,7 +42,6 @@ Section-level elements are used to group the information within the query help f
4242

4343
For further information about the other section-level, block, list and table elements supported by query help files, see [Query help files](https://codeql.github.com/docs/writing-codeql-queries/query-help-files/) on codeql.github.com.
4444

45-
4645
## English style
4746

4847
You should write the overview and recommendation elements in simple English that is easy to follow. You should:
@@ -98,7 +97,6 @@ If you are citing an academic paper, we recommend adopting the reference style o
9897

9998
>S. R. Chidamber and C. F. Kemerer, _A metrics suite for object-oriented design_. IEEE Transactions on Software Engineering, 20(6):476-493, 1994.
10099
101-
102100
### Websites
103101

104102
If you are citing a website, please use the following format, without breadcrumb trails:
@@ -154,13 +152,13 @@ later. For example, it's easy to see at a glance which part of the code is in th
154152
scope of an <code>if</code> statement, and adding more statements to the body of the <code>if</code>
155153
statement is less error-prone.</p>
156154

157-
<p>You should also ensure that the indentation of the code is consistent with the actual flow of
155+
<p>You should also ensure that the indentation of the code is consistent with the actual flow of
158156
control, so that it does not confuse programmers.</p>
159157

160158
</recommendation>
161159
<example>
162160

163-
<p>In the example below, the original version of <code>Cart</code> is missing braces. This means
161+
<p>In the example below, the original version of <code>Cart</code> is missing braces. This means
164162
that the code triggers a <code>NullPointerException</code> at runtime if <code>i</code>
165163
is <code>null</code>.</p>
166164

0 commit comments

Comments
 (0)