summaryrefslogtreecommitdiff
path: root/docs/userguide/introduction.rst
diff options
context:
space:
mode:
authorAsk Solem <ask@celeryproject.org>2016-07-29 19:37:05 -0700
committerAsk Solem <ask@celeryproject.org>2016-07-29 19:37:05 -0700
commitfcb7ca06c884afa18bf3bce23795ae373fe2a368 (patch)
treef42dbc11cc7c022e3dcb3ce6b436e4b761b14f02 /docs/userguide/introduction.rst
parentd9340c1f3b6660c596ee35eba943336e91eb5dd8 (diff)
downloadkombu-fcb7ca06c884afa18bf3bce23795ae373fe2a368.tar.gz
One space after period for proportional fonts
Diffstat (limited to 'docs/userguide/introduction.rst')
-rw-r--r--docs/userguide/introduction.rst18
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/userguide/introduction.rst b/docs/userguide/introduction.rst
index b540e1e3..0023c6d0 100644
--- a/docs/userguide/introduction.rst
+++ b/docs/userguide/introduction.rst
@@ -11,7 +11,7 @@ What is messaging?
In times long ago people didn't have email.
They had the postal service, which with great courage would deliver mail
-from hand to hand all over the globe. Soldiers deployed at wars far away could only
+from hand to hand all over the globe. Soldiers deployed at wars far away could only
communicate with their families through the postal service, and
posting a letter would mean that the recipient wouldn't actually
receive the letter until weeks or months, sometimes years later.
@@ -24,8 +24,8 @@ be news to anyone, but why would applications?
One example is banks.
When you transfer money from one bank to another, your bank sends
-a message to a central clearinghouse. The clearinghouse
-then records and coordinates the transaction. Banks
+a message to a central clearinghouse. The clearinghouse
+then records and coordinates the transaction. Banks
need to send and receive millions and millions of
messages every day, and losing a single message would mean either losing
your money (bad) or the banks money (very bad)
@@ -34,7 +34,7 @@ Another example is the stock exchanges, which also have a need
for very high message throughputs and have strict reliability
requirements.
-Email is a great way for people to communicate. It is much faster
+Email is a great way for people to communicate. It is much faster
than using the postal service, but still using email as a means for
programs to communicate would be like the soldier above, waiting
for signs of life from his girlfriend back home.
@@ -48,7 +48,7 @@ Messaging Scenarios
The request/reply pattern works like the postal service example.
A message is addressed to a single recipient, with a return address
- printed on the back. The recipient may or may not reply to the
+ printed on the back. The recipient may or may not reply to the
message by sending it back to the original sender.
Request-Reply is achieved using *direct* exchanges.
@@ -67,7 +67,7 @@ Messaging Scenarios
interested in.
If no consumers subscribe to the topic, then the message
- will not be delivered to anyone. If several consumers
+ will not be delivered to anyone. If several consumers
subscribe to the topic, then the message will be delivered
to all of them.
@@ -78,8 +78,8 @@ Messaging Scenarios
Reliability
===========
-For some applications reliability is very important. Losing a message is
-a critical situation that must never happen. For other applications
+For some applications reliability is very important. Losing a message is
+a critical situation that must never happen. For other applications
losing a message is fine, it can maybe recover in other ways,
or the message is resent anyway as periodic updates.
@@ -92,7 +92,7 @@ AMQP defines two built-in delivery modes:
* transient
Messages may or may not be written to disk, as the broker sees fit
- to optimize memory contents. The messages will not survive a broker
+ to optimize memory contents. The messages won't survive a broker
restart.
Transient messaging is by far the fastest way to send and receive messages,