Skip to content

Commit bf6f8d3

Browse files
committed
Removing forced line breaks
1 parent 043ad50 commit bf6f8d3

File tree

1 file changed

+5
-10
lines changed

1 file changed

+5
-10
lines changed

README.md

+5-10
Original file line numberDiff line numberDiff line change
@@ -973,8 +973,7 @@ We use hyphen-delimited for:
973973

974974
### Namespace
975975

976-
Mostly everything in our CSS is namespaced so that our CSS is as transparent
977-
and self-documenting as possible.
976+
Mostly everything in our CSS is namespaced so that our CSS is as transparent and self-documenting as possible.
978977

979978
#### What We Namespace
980979

@@ -1037,8 +1036,7 @@ And the rest:
10371036

10381037
Rather than rehashing everything about JS hooks let's instead defer to the [JavaScript Hooks](http://cssguidelin.es/#javascript-hooks) section in [Harry Roberts](http://csswizardry.com/) excellent [CSS Guidelines](http://cssguidelin.es/).
10391038

1040-
JS hooks—and [Server-side](#server-side-hooks), [QA](#qa-hooks), and [Tracking hooks](#tracking-hooks)—should always be scoped to the component it is part
1041-
off to avoid clashing with other hooks of the same category, and to keep them highly readable—not much different to how we structure our classes for styling.
1039+
JS hooks—and [Server-side](#server-side-hooks), [QA](#qa-hooks), and [Tracking hooks](#tracking-hooks)—should always be scoped to the component it is part off to avoid clashing with other hooks of the same category, and to keep them highly readable—not much different to how we structure our classes for styling.
10421040

10431041
###### :heavy_multiplication_x: NOT GOOD
10441042

@@ -1317,13 +1315,11 @@ Making it easier to apply our guidelines and to prevent wasting time picking apa
13171315

13181316
We recommend using the excellent [stylelint](http://stylelint.io/) CSS linter.
13191317

1320-
You'll be able to create a configuration file that enforces pretty much all
1321-
of these guidelines. Stand by for such a file.
1318+
You'll be able to create a configuration file that enforces pretty much all of these guidelines. Stand by for such a file.
13221319

13231320
### EditorConfig
13241321

1325-
We use an [EditorConfig](http://editorconfig.org) file which enforces our
1326-
indenting rules.
1322+
We use an [EditorConfig](http://editorconfig.org) file which enforces our indenting rules.
13271323

13281324
The contents of the `.editorconfig` file should look something like this:
13291325

@@ -1341,8 +1337,7 @@ insert_final_newline = true
13411337

13421338
### Text Editor Configuration
13431339

1344-
You should configure your text editor to adhere to as much of these guidelines
1345-
as possible.
1340+
You should configure your text editor to adhere to as much of these guidelines as possible.
13461341

13471342
At the bare minimum configure your editor to *show invisibles* or to automatically remove end-of-line whitespace.
13481343

0 commit comments

Comments
 (0)