Skip to content

Commit

Permalink
Fix typos and improve language (#1149)
Browse files Browse the repository at this point in the history
  • Loading branch information
preciz authored and sorentwo committed Sep 10, 2024
1 parent 6770763 commit cc89021
Show file tree
Hide file tree
Showing 6 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ a `pid` via observer or live dashboard.

- [Repo] Automatically retry all transactions with backoff.

Avoid both expected an unexpected database errors by automatically retrying transactions. Some
Avoid both expected and unexpected database errors by automatically retrying transactions. Some
operations, such as serialization and lock not available errors, are likely to occur during
standard use depending on how a database is configured. Other errors happen infrequently due to
pool contention or flickering connections, and those should also be retried for increased
Expand Down
2 changes: 1 addition & 1 deletion SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
Oban applies bug fixes only to the latest minor version. Security patches are
available for the last 3 minor versions:

| Oban Wersion | Support |
| Oban Version | Support |
| ------------ | ------------------------------ |
| 2.17 | Bug fixes and security patches |
| 2.16 | Security patches only |
Expand Down
2 changes: 1 addition & 1 deletion guides/preparing_for_production.md
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ For additional observability and introspection, consider integrating with one of
tools built on `Oban.Telemetry`:

* [Oban Web](https://getoban.pro)—an official Oban package, it's a view of jobs, queues, and
metrics that you host directly within your application. Powered by Phoenix Live View and Oban
metrics that you host directly within your application. Powered by Phoenix LiveView and Oban
Metrics, it is extremely lightweight and continuously updated.

* [PromEx](https://hex.pm/packages/prom_ex)—Prometheus metrics and Grafana dashboards based on
Expand Down
2 changes: 1 addition & 1 deletion guides/recipes/splitting-queues.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ pairs and separated by spaces. For example, to run only the `default` and
Note that the parsing clause has a couple of safety mechanisms to ensure that
only real queues are specified:

1. It automatically trims while splitting values, so extra whitespace like won't
1. It automatically trims while splitting values, so extra whitespace won't
break parsing (i.e. ` default,3 `)
2. It only converts the `queue` string to _an existing atom_, hopefully
preventing typos that would start a random queue (i.e. `default`)
Expand Down
2 changes: 1 addition & 1 deletion guides/release_configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ end
Our config provider ensures that the `Jason` app is loaded so that we can parse
a `JSON` configuration file. Once the JSON is loaded we must extract the
`queues` map and convert it to a keyword list where all of the keys are atoms.
The use of `String.to_atom/1` is safe because all of our queues names are
The use of `String.to_atom/1` is safe because all of our queue names are
already defined.

Then you include this in your `mix.exs` file, where your release is configured:
Expand Down
2 changes: 1 addition & 1 deletion guides/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ config :my_app, Oban,

Sometimes `Cron` or `Pruner` plugins appear to stop working unexpectedly. Typically, this happens in
systems with multi-node setups where "web" nodes only enqueue jobs while "worker" nodes are
configured to run queues and plugins. Most plugins require leadership to function, so When a "web"
configured to run queues and plugins. Most plugins require leadership to function, so when a "web"
node becomes leader the plugins go dormant.

The solution is to disable leadership with `peer: false` on any node that doesn't run plugins:
Expand Down

0 comments on commit cc89021

Please sign in to comment.