ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-07-22 12:50:22 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

doc(user_guide): fix typos (#47425)

Browse source
This commit is contained in:
Simon Legner 2018-10-24 18:01:24 +02:00 • committed by Sandra McCann
commit 5959158612
9 changed files with 12 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/docsite/rst/user_guide/windows_usage.rst
View file

@ -273,7 +273,7 @@ rules apply:
* A double quote preceded by a backslash ``\`` is interpreted as just a double
quote ``"`` and not as an argument delimiter.
* Backslashes are interpreted literally unless it immediately preceeds double
* Backslashes are interpreted literally unless it immediately precedes double
quotes; for example ``\`` == ``\`` and ``\"`` == ``"``
* If an even number of backslashes is followed by a double quote, one
@ -294,7 +294,7 @@ With those rules in mind, here are some examples of quoting::
argv[3] = C:\path\with space
argv[4] = double "quoted"
- win_command: '"C:\Program Files\Program\program.exe" "escaped \\\" backslash" unqouted-end-backslash\'
- win_command: '"C:\Program Files\Program\program.exe" "escaped \\\" backslash" unquoted-end-backslash\'
argv[0] = C:\Program Files\Program\program.exe
argv[1] = escaped \" backslash
@ -412,7 +412,7 @@ Here are some examples on how to write Windows paths::
Legacy key=value Style
----------------------
The legacy ``key=value`` syntax is used on the command line for adhoc commands,
The legacy ``key=value`` syntax is used on the command line for ad-hoc commands,
or inside playbooks. The use of this style is discouraged within playbooks
because backslash characters need to be escaped, making playbooks harder to read.
The legacy syntax depends on the specific implementation in Ansible, and quoting