Merge branch 'tarikdemirci-patch-1'

Author: michaelklishin

docs/persistence-conf.md

@@ -87,7 +87,7 @@ raft.wal_max_size_bytes = 32000000
 
 :::important
 
-Because memory is not guaranteed to be deadllocated instaltly by the [runtime](./runtime/),
+Because memory is not guaranteed to be deallocated instantly by the [runtime](./runtime/),
 we recommend that the RabbitMQ node is allocated at least 3 times the memory of the effective WAL file size limit.
 More will be required in high-throughput systems.
 4 times is a good starting point for those.

docs/quorum-queues/index.md

@@ -1164,7 +1164,7 @@ footprint can reach 512 MiB. You can expect your memory usage to look like this:
 ![Quorum Queues memory usage pattern](./quorum-queue-memory-usage-pattern.png)
 </figure>
 
-Because memory is not guaranteed to be deadllocated instaltly by the [runtime](./runtime/),
+Because memory is not guaranteed to be deallocated instantly by the [runtime](./runtime/),
 we recommend that the RabbitMQ node is allocated at least 3 times the memory of the default WAL file size limit.
 More will be required in high-throughput systems. 4 times is a good starting point for those.
 

versioned_docs/version-3.13/persistence-conf.md

@@ -87,7 +87,7 @@ raft.wal_max_size_bytes = 32000000
 
 :::important
 
-Because memory is not guaranteed to be deadllocated instaltly by the [runtime](./runtime/),
+Because memory is not guaranteed to be deallocated instantly by the [runtime](./runtime/),
 we recommend that the RabbitMQ node is allocated at least 3 times the memory of the effective WAL file size limit.
 More will be required in high-throughput systems.
 4 times is a good starting point for those.

versioned_docs/version-3.13/quorum-queues/index.md

@@ -1078,7 +1078,7 @@ footprint can reach 512 MiB. You can expect your memory usage to look like this:
 ![Quorum Queues WAL memory usage pattern](./quorum-queue-memory-usage-pattern.png)
 </figure>
 
-Because memory is not guaranteed to be deadllocated instaltly by the [runtime](./runtime/),
+Because memory is not guaranteed to be deallocated instantly by the [runtime](./runtime/),
 we recommend that the RabbitMQ node is allocated at least 3 times the memory of the default WAL file size limit.
 More will be required in high-throughput systems. 4 times is a good starting point for those.
 

versioned_docs/version-4.0/persistence-conf.md

@@ -87,7 +87,7 @@ raft.wal_max_size_bytes = 32000000
 
 :::important
 
-Because memory is not guaranteed to be deadllocated instaltly by the [runtime](./runtime/),
+Because memory is not guaranteed to be deallocated instantly by the [runtime](./runtime/),
 we recommend that the RabbitMQ node is allocated at least 3 times the memory of the effective WAL file size limit.
 More will be required in high-throughput systems.
 4 times is a good starting point for those.

versioned_docs/version-4.0/quorum-queues/index.md

@@ -1167,7 +1167,7 @@ footprint can reach 512 MiB. You can expect your memory usage to look like this:
 
 :::important
 
-Because memory is not guaranteed to be deadllocated instaltly by the [runtime](./runtime/),
+Because memory is not guaranteed to be deallocated instantly by the [runtime](./runtime/),
 we recommend that the RabbitMQ node is allocated at least 3 times the memory of the effective WAL file size limit.
 More will be required in high-throughput systems.
 4 times is a good starting point for those.