Browse code

Fix some typos (#16498)

Shota authored on 2016/06/30 03:31:25
Showing 11 changed files
... ...
@@ -2,7 +2,7 @@
2 2
 #
3 3
 
4 4
 # Define an Abiquo user with access to Abiquo API which will be used to
5
-# perform required queries to obtain infromation to generate the Ansible
5
+# perform required queries to obtain information to generate the Ansible
6 6
 # inventory output.
7 7
 #
8 8
 [auth]
... ...
@@ -127,7 +127,7 @@ Don't query the galaxy API when creating roles
127 127
 LIST
128 128
 ----
129 129
 
130
-The *list* sub-command is used to show what roles are currently instaled.
130
+The *list* sub-command is used to show what roles are currently installed.
131 131
 You can specify a role name, and if installed only that role will be shown.
132 132
 
133 133
 USAGE
... ...
@@ -334,7 +334,7 @@ Override the default server https://galaxy.ansible.com.
334 334
 
335 335
 --list::
336 336
 
337
-Show your configured integrations. Provids the ID of each integration
337
+Show your configured integrations. Provides the ID of each integration
338 338
 which can be used with the remove option.
339 339
 
340 340
 --remove::
... ...
@@ -144,7 +144,7 @@ Run operations with su (deprecated, use become).
144 144
 
145 145
 *-R SU-USER*, *--su-user=*'SU_USER'::
146 146
 
147
-run operations with su as this user (default=root) (deprecated, use become).
147
+Run operations with su as this user (default=root) (deprecated, use become).
148 148
 
149 149
 *-s*, *--sudo*::
150 150
 
... ...
@@ -52,7 +52,7 @@ the password.
52 52
 Show a help message related to the given sub-command.
53 53
 
54 54
 
55
-If '--valut-password-file' is not supplied ansib-vault will automatically prompt for passwords as required.
55
+If '--vault-password-file' is not supplied ansible-vault will automatically prompt for passwords as required.
56 56
 
57 57
 
58 58
 CREATE
... ...
@@ -104,7 +104,7 @@ Show help message and exit.
104 104
 *-i* 'PATH', *--inventory=*'PATH'::
105 105
 
106 106
 The 'PATH' to the inventory, which defaults to '/etc/ansible/hosts'.
107
-Alternatively you can use a comma separated list of hosts or single host with traling comma 'host,'.
107
+Alternatively you can use a comma separated list of hosts or single host with trailing comma 'host,'.
108 108
 
109 109
 *-l* 'SUBSET', *--limit=*'SUBSET'::
110 110
 
... ...
@@ -14,7 +14,7 @@ notes:
14 14
 requirements:
15 15
     - list of required things
16 16
     - like the factor package
17
-    - or a specic platform
17
+    - or a specific platform
18 18
 options:
19 19
 # One or more of the following
20 20
     option_name:
... ...
@@ -30,7 +30,7 @@
30 30
 ##      192.168.1.110:
31 31
 
32 32
 # Ex 3: You can create hosts using ranges and add children groups and vars to a group
33
-# The child group can define anything you would normall add to a group
33
+# The child group can define anything you would normally add to a group
34 34
 
35 35
 ##testing:
36 36
 ##  hosts:
... ...
@@ -7,7 +7,7 @@ from ansible.playbook.play import Play
7 7
 from ansible.executor.task_queue_manager import TaskQueueManager
8 8
 from ansible.plugins.callback import CallbackBase
9 9
 
10
-# Creat a callback object so we can capture the output
10
+# Create a callback object so we can capture the output
11 11
 class ResultsCollector(CallbackBase):
12 12
 
13 13
     def __init__(self, *args, **kwargs):
... ...
@@ -68,7 +68,7 @@ class AnsibleError(Exception):
68 68
 
69 69
     def _get_error_lines_from_file(self, file_name, line_number):
70 70
         '''
71
-        Returns the line in the file which coresponds to the reported error
71
+        Returns the line in the file which corresponds to the reported error
72 72
         location, as well as the line preceding it (if the error did not
73 73
         occur on the first line), to provide context to the error.
74 74
         '''
... ...
@@ -14,7 +14,7 @@ open dialog.  You can stop by the development list, and we'd be glad to talk abo
14 14
 
15 15
    * https://groups.google.com/forum/#!forum/ansible-devel
16 16
 
17
-In the future, sometimes starting a discussion on the development list prior to implenting a feature can make getting things included a little easier, but it's not always necessary.
17
+In the future, sometimes starting a discussion on the development list prior to implementing a feature can make getting things included a little easier, but it's not always necessary.
18 18
 
19 19
 Thank you once again for this and your interest in Ansible!
20 20
 
... ...
@@ -15,7 +15,7 @@ However, we're absolutely always up for discussion.  Since this is a really busy
15 15
 
16 16
    * https://groups.google.com/forum/#!forum/ansible-devel
17 17
 
18
-In the future, sometimes starting a discussion on the development list prior to implenting a feature can make getting things included a little easier, but it's not always necessary.
18
+In the future, sometimes starting a discussion on the development list prior to implementing a feature can make getting things included a little easier, but it's not always necessary.
19 19
 
20 20
 Thank you once again for this and your interest in Ansible!
21 21