This is an automated email from the ASF dual-hosted git repository.
jbertram pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-website.git
The following commit(s) were added to refs/heads/main by this push:
new 99d66e263 grammar fix
99d66e263 is described below
commit 99d66e263055b506b92491886562ea8a4a574b47
Author: Justin Bertram <[email protected]>
AuthorDate: Mon Aug 21 08:16:17 2023 -0500
grammar fix
---
src/async-sends.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/async-sends.md b/src/async-sends.md
index f0b2c3163..5234cc774 100644
--- a/src/async-sends.md
+++ b/src/async-sends.md
@@ -17,7 +17,7 @@ The good news is that ActiveMQ sends message in async mode by
default in several
If you are not using transactions and are sending persistent messages, then
each send is synch and blocks until the broker has sent back an acknowledgement
to the producer that the message has been safely persisted to disk. This ack
provides that guarantee that the message will not be lost but it also costs a
huge latency penalty since the client is blocked.
-Many high performance applications are designed to be tolerate a small amount
of message loss in failure scenarios. If your application has been designed in
this fashion, you can enable the use of async sends to increase throughput even
when using persistent messages.
+Many high performance applications are designed to tolerate a small amount of
message loss in failure scenarios. If your application has been designed in
this fashion, you can enable the use of async sends to increase throughput even
when using persistent messages.
### Configuring Async Send using a Connection URI
