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 f09dcfbaf fix grammar
f09dcfbaf is described below
commit f09dcfbafcea1f119629c10d9d08ce08cd437ec3
Author: Justin Bertram <[email protected]>
AuthorDate: Mon Aug 21 08:17:00 2023 -0500
fix grammar
---
src/components/nms/providers/activemq/advanced-features/async-sends.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/src/components/nms/providers/activemq/advanced-features/async-sends.md
b/src/components/nms/providers/activemq/advanced-features/async-sends.md
index 6a32cf31c..a83ba21b4 100644
--- a/src/components/nms/providers/activemq/advanced-features/async-sends.md
+++ b/src/components/nms/providers/activemq/advanced-features/async-sends.md
@@ -14,7 +14,7 @@ The good news is that Apache.NMS.ActiveMQ sends message in
async mode by default
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
