Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix several typos on the advanced-usage page #3174

Merged
merged 1 commit into from
Feb 13, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/advanced-usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -1133,7 +1133,7 @@ events is:
`ConnectionDeactivatedEvent`

5. Since 5.3: Reconnect failed: A reconnect attempt failed. Contains
the reconnect failure and and the retry counter. Event type:
the reconnect failure and the retry counter. Event type:
`ReconnectFailedEvent`

#### Metrics events
Expand Down Expand Up @@ -2515,7 +2515,7 @@ Commands that are issued as long as the failure persists are buffered.

#### Exceptions to *at-least-once*

Lettuce does not loose commands while sending them. A command execution
Lettuce does not lose commands while sending them. A command execution
can, however, fail for the same reasons as a normal method call can on
the JVM:

Expand Down Expand Up @@ -2558,7 +2558,7 @@ from the response queue, and the connection stays usable.

In general, when `Errors` occur while operating on a connection, you
should close the connection and use a new one. Connections, that
experienced such severe failures get into a unrecoverable state, and no
experienced such severe failures get into an unrecoverable state, and no
further response processing is possible.

Executing commands more than once
Expand Down