Skip to content

Commit 57933e9

Browse files
committed
Comma cleanup
1 parent 85864ec commit 57933e9

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

doc/topics/transports/raet/index.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,8 @@ Using RAET in Salt
2929
==================
3030

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

doc/topics/transports/raet/programming_intro.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Intro to RAET Programming
77
This page is still under construction
88

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

0 commit comments

Comments
 (0)