fix a few documentation typos

smallrye · Nov 27, 2024 · 32aaa4a · 32aaa4a
1 parent ee81b70
commit 32aaa4a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/doc/modules/ROOT/pages/reference/bulkhead.adoc b/doc/modules/ROOT/pages/reference/bulkhead.adoc
@@ -6,7 +6,7 @@ For introduction, see xref:howto/bulkhead.adoc[How to Limit Concurrency].
 
 If a guarded method is called by too many callers concurrently, the excess attempts will fail with `BulkheadException`.
 
-If the gaurded method is `@Asynchronous` or `@AsynchronousNonBlocking`, excess attempts are first put into a queue.
+If the guarded method is `@Asynchronous` or `@AsynchronousNonBlocking`, excess attempts are first put into a queue.
 The queued attempts are executed later.
 When the queue becomes full, excess attempts are rejected with `BulkheadException`.
 

diff --git a/doc/modules/ROOT/pages/reference/timeout.adoc b/doc/modules/ROOT/pages/reference/timeout.adoc
@@ -6,11 +6,11 @@ For introduction, see xref:howto/timeout.adoc[How to Watch for Timeouts].
 
 If a guarded method takes too long, the caller will get a `TimeoutException`.
 
-If the gaurded method is not `@Asynchronous` or `@AsynchronousNonBlocking`, the thread executing the method is interrupted.
+If the guarded method is not `@Asynchronous` or `@AsynchronousNonBlocking`, the thread executing the method is interrupted.
 Note that interruption requires cooperation from the executing code (for example, it must not swallow `InterruptedException`).
 In other words, it is not guaranteed that interrupting the method will actually make it stop.
 
-If the gaurded method is `@Asynchronous` or `@AsynchronousNonBlocking`, timeout is always signalled correctly, but there is no cancellation.
+If the guarded method is `@Asynchronous` or `@AsynchronousNonBlocking`, timeout is always signalled correctly, but there is no cancellation.
 Even after timeout, the asynchronous action will keep running; its eventual result is just ignored.
 
 [[interactions]]