mirror of
https://github.com/saltstack/salt.git
synced 2025-04-17 10:10:20 +00:00
Fix various spelling mistakes
This commit is contained in:
parent
371b0a86d9
commit
9a51ba5c5b
10 changed files with 13 additions and 13 deletions
|
@ -459,7 +459,7 @@ Aliasing Functions
|
|||
|
||||
Sometimes one wishes to use a function name that would shadow a python built-in.
|
||||
A common example would be ``set()``. To support this, append an underscore to
|
||||
the function defintion, ``def set_():``, and use the ``__func_alias__`` feature
|
||||
the function definition, ``def set_():``, and use the ``__func_alias__`` feature
|
||||
to provide an alias to the function.
|
||||
|
||||
``__func_alias__`` is a dictionary where each key is the name of a function in
|
||||
|
|
|
@ -38,7 +38,7 @@ Changes:
|
|||
|
||||
- **PR** `#27516`_: (*basepi*) [2015.5] Merge forward from 2014.7 to 2015.5
|
||||
|
||||
- **PR** `#27472`_: (*cachedout*) Change recommeded schema for data field in mysql event table
|
||||
- **PR** `#27472`_: (*cachedout*) Change recommended schema for data field in mysql event table
|
||||
|
||||
- **PR** `#27468`_: (*cachedout*) Fix 27351
|
||||
|
||||
|
|
|
@ -290,7 +290,7 @@ Thorium - Provisional New Reactor
|
|||
---------------------------------
|
||||
|
||||
The 2016.3 release introduces the new Thorium Reactor. This reactor is an
|
||||
experimental new feature that implements a flow programing interface using
|
||||
experimental new feature that implements a flow programming interface using
|
||||
the salt state system as the engine. This means that the Thorium reactor uses
|
||||
a classic state tree approach to create a reactor that can aggregate event
|
||||
data from multiple sources and make aggregate decisions about executing
|
||||
|
|
|
@ -18,7 +18,7 @@ standard ``salt`` commands.
|
|||
- Python is required on the remote system (unless using the ``-r`` option to send raw ssh commands)
|
||||
- On many systems, the ``salt-ssh`` executable will be in its own package, usually named
|
||||
``salt-ssh``
|
||||
- The Salt SSH system does not supercede the standard Salt communication
|
||||
- The Salt SSH system does not supersede the standard Salt communication
|
||||
systems, it simply offers an SSH-based alternative that does not require
|
||||
ZeroMQ and a remote agent. Be aware that since all communication with Salt SSH is
|
||||
executed via SSH it is substantially slower than standard Salt with ZeroMQ.
|
||||
|
@ -183,7 +183,7 @@ Salt SSH with a regular user you have to modify some paths or you will get
|
|||
"Permission denied" messages. You have to modify two parameters: ``pki_dir``
|
||||
and ``cachedir``. Those should point to a full path writable for the user.
|
||||
|
||||
It's recommed not to modify /etc/salt for this purpose. Create a private copy
|
||||
It's recommended not to modify /etc/salt for this purpose. Create a private copy
|
||||
of /etc/salt for the user and run the command with ``-c /new/config/path``.
|
||||
|
||||
Define CLI Options with Saltfile
|
||||
|
|
|
@ -257,7 +257,7 @@ def create_user(username, password, permissions, users=None):
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
salt dell drac.create_user [USERNAME] [PASSWORD] [PRIVELEGES]
|
||||
salt dell drac.create_user [USERNAME] [PASSWORD] [PRIVILEGES]
|
||||
salt dell drac.create_user diana secret login,test_alerts,clear_logs
|
||||
|
||||
DRAC Privileges
|
||||
|
@ -320,7 +320,7 @@ def set_permissions(username, permissions, uid=None):
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
salt dell drac.set_permissions [USERNAME] [PRIVELEGES] [USER INDEX - optional]
|
||||
salt dell drac.set_permissions [USERNAME] [PRIVILEGES] [USER INDEX - optional]
|
||||
salt dell drac.set_permissions diana login,test_alerts,clear_logs 4
|
||||
|
||||
DRAC Privileges
|
||||
|
|
|
@ -548,7 +548,7 @@ def create_user(username, password, permissions,
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
salt dell dracr.create_user [USERNAME] [PASSWORD] [PRIVELEGES]
|
||||
salt dell dracr.create_user [USERNAME] [PASSWORD] [PRIVILEGES]
|
||||
salt dell dracr.create_user diana secret login,test_alerts,clear_logs
|
||||
|
||||
DRAC Privileges
|
||||
|
@ -616,7 +616,7 @@ def set_permissions(username, permissions,
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
salt dell dracr.set_permissions [USERNAME] [PRIVELEGES]
|
||||
salt dell dracr.set_permissions [USERNAME] [PRIVILEGES]
|
||||
[USER INDEX - optional]
|
||||
salt dell dracr.set_permissions diana login,test_alerts,clear_logs 4
|
||||
|
||||
|
|
|
@ -704,7 +704,7 @@ def set_bootdev(bootdev='default', persist=False, uefiboot=False, **kwargs):
|
|||
this
|
||||
|
||||
:param uefiboot: If true, request UEFI boot explicitly. Strictly
|
||||
speaking, the spec sugests that if not set, the system
|
||||
speaking, the spec suggests that if not set, the system
|
||||
should BIOS boot and offers no "don't care" option.
|
||||
In practice, this flag not being set does not preclude
|
||||
UEFI boot on any system I've encountered.
|
||||
|
|
|
@ -541,7 +541,7 @@ def list_updates(verbose=False, fields=None, skips=None, retries=5, categories=N
|
|||
fields
|
||||
Return a list of specific fields for each update. The optional
|
||||
values here are those at the root level of the verbose list. This
|
||||
is superceded by the verbose option.
|
||||
is superseded by the verbose option.
|
||||
|
||||
retries
|
||||
Number of retries to make before giving up. This is total, not per
|
||||
|
|
|
@ -911,7 +911,7 @@ def create_certificate(path=None, text=False, ca_server=None, **kwargs):
|
|||
- x509.sign_remote_certificate
|
||||
|
||||
subject properties:
|
||||
Any of the values below can be incldued to set subject properties
|
||||
Any of the values below can be included to set subject properties
|
||||
Any other subject properties supported by OpenSSL should also work.
|
||||
|
||||
C:
|
||||
|
|
|
@ -227,7 +227,7 @@ documentation, but in short:
|
|||
<salt.wheel.key>` exposes similar functionality as the ``salt-key`` CLI
|
||||
command.
|
||||
|
||||
Most clients have variants like synchronous or asyncronous execution as well as
|
||||
Most clients have variants like synchronous or asynchronous execution as well as
|
||||
others like batch execution. See the :ref:`full list of client interfaces
|
||||
<netapi-clients>`.
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue