valitydev/salt
14
0
Fork 0
mirror of https://github.com/valitydev/salt.git synced 2024-11-07 08:58:59 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Comma cleanup

Browse Source
This commit is contained in:
Thomas Jackson 2014-12-12 11:38:18 -08:00
parent 85864eca4a
commit 57933e9148
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/topics/transports/raet/index.rst
View File

@ -29,8 +29,8 @@ Using RAET in Salt
==================
Using RAET in Salt is easy, the main difference is that the core dependencies
change, instead of needing pycrypto, M2Crypto, ZeroMQ and PYZMQ, the packages
libsodium, libnacl, ioflo and raet are required. Encryption is handled very cleanly
change, instead of needing pycrypto, M2Crypto, ZeroMQ, and PYZMQ, the packages
libsodium, libnacl, ioflo, and raet are required. Encryption is handled very cleanly
by libnacl, while the queueing and flow control is handled by
ioflo. Distribution packages are forthcoming, but libsodium can be easily
installed from source, or many distributions do ship packages for it.

2
doc/topics/transports/raet/programming_intro.rst
View File

@ -7,7 +7,7 @@ Intro to RAET Programming
This page is still under construction
The first thing to cover is that RAET does not present a socket api, it
presents and queueing api, all messages in RAET are made available to via
presents, and queueing api, all messages in RAET are made available to via
queues. This is the single most differentiating factor with RAET vs other
networking libraries, instead of making a socket, a stack is created.
Instead of calling send() or recv(), messages are placed on the stack to be