mirror of
https://github.com/valitydev/salt.git
synced 2024-11-07 00:55:19 +00:00
Fix trivial grammar and spelling errors in the doc
This commit is contained in:
parent
dd10fdc8ba
commit
e39c3e29b4
@ -16,7 +16,7 @@ To expand on this a little:
|
||||
|
||||
There is much argument over the actual definition of "open core". From our standpoint, Salt is open source because
|
||||
|
||||
1. It is a standalone product that that anyone is free to use.
|
||||
1. It is a standalone product that anyone is free to use.
|
||||
2. It is developed in the open with contributions accepted from the community for the good of the project.
|
||||
3. There are no features of Salt itself that are restricted to separate proprietary products distributed by SaltStack, Inc.
|
||||
4. Because of our Apache 2.0 license, Salt can be used as the foundation for a project or even a proprietary tool.
|
||||
|
@ -97,8 +97,8 @@ Glossary
|
||||
evaluated. *See also*: :ref:`state layers <state-layers-low-state>`.
|
||||
|
||||
Master
|
||||
A central Salt daemon which from which commands can be issued to
|
||||
listening minions.
|
||||
A central Salt daemon from which commands can be issued to listening
|
||||
minions.
|
||||
|
||||
Masterless
|
||||
A minion which does not require a Salt master to operate. All
|
||||
|
@ -45,7 +45,7 @@ sent through the started daemons.
|
||||
Integration tests are particularly good at testing modules, states, and
|
||||
shell commands, among other segments of Salt's ecosystem. By utilizing
|
||||
the integration test daemons, integration tests are easy to write. They
|
||||
are also SaltStack's gerneally preferred method of adding new tests.
|
||||
are also SaltStack's generally preferred method of adding new tests.
|
||||
|
||||
The discussion in the :ref:`Integration vs. Unit <integration-vs-unit>`
|
||||
section of the :ref:`testing tutorial <tutorial-salt-testing>` is
|
||||
|
Loading…
Reference in New Issue
Block a user