Skip to content

Commit e16291c

Browse files
vegarHonkingGoose
authored andcommitted
Improve language
Correct usage of braces vs brackets Rewrite first sentence to flow better, and to explain the braces situation a bit better. Remove "either" from the second sentence, as I think the sentence is better without that word. The "or" in the middle of the sentence makes it clear that there are two choices to deal with the bracket issue. So "either" is not really adding value. Co-authored-by: HonkingGoose <[email protected]>
1 parent edf81f0 commit e16291c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

book/07-git-tools/sections/revision-selection.asc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -181,11 +181,11 @@ If you have a UNIX or Linux background, you can think of the reflog as Git's ver
181181
====
182182

183183
[NOTE]
184-
.Escaping brackets in PowerShell
184+
.Escaping braces in PowerShell
185185
====
186186
187-
On Windows in `powershell.exe`, `{` and `}` are special characters and needs to be treated differently.
188-
You can either escape them with a backtick ` or put the commit reference in quotes:
187+
When using PowerShell on Windows, braces like `{` and `}` are special characters and must be escaped.
188+
You can escape them with a backtick ` or put the commit reference in quotes:
189189
190190
[source,console]
191191
----

0 commit comments

Comments
 (0)