From cf58bc826a885c28f0d2e760221c505ddfd16757 Mon Sep 17 00:00:00 2001 From: Kian-Meng Ang Date: Mon, 12 Dec 2022 12:37:54 +0800 Subject: [PATCH] Fix typos Found via `codespell -S deps` --- CHANGELOG.md | 2 +- guides/libcluster.md | 4 ++-- lib/horde/distribution_strategy.ex | 2 +- test/registry_test.exs | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 72c2dd37..5a8f2a9e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -46,6 +46,6 @@ ## 0.6.0 - `Horde.Supervisor` now behaves more like `DynamicSupervisor`. [#122](https://github.com/derekkraan/horde/pull/122) - `Horde.Registry` sends an exit signal to the process that "loses" when a conflict is resolved. [#118](https://github.com/derekkraan/horde/pull/118) -- `Horde.Registry.register/3` returns `{:error, {:already_registered, pid}}` when applicable. This improves compatability with `Elixir.Registry`. [#115](https://github.com/derekkraan/horde/pull/115) +- `Horde.Registry.register/3` returns `{:error, {:already_registered, pid}}` when applicable. This improves compatibility with `Elixir.Registry`. [#115](https://github.com/derekkraan/horde/pull/115) - Adds `Horde.Registry.select/2`, which works the same as `Elixir.Registry.select/2`, which will land in Elixir 1.9. [#110](https://github.com/derekkraan/horde/pull/110) - Fixes a bug causing `Horde.Supervisor` to crash if a child process was restarting when `Horde.Supervisor.delete_child/2` was called. [#114](https://github.com/derekkraan/horde/pull/114) diff --git a/guides/libcluster.md b/guides/libcluster.md index 314ee22c..48d546f7 100644 --- a/guides/libcluster.md +++ b/guides/libcluster.md @@ -133,7 +133,7 @@ defmodule NodeListener do end ``` -Note that the funcionality provided in this example is essentially the same as +Note that the functionality provided in this example is essentially the same as the [`members: :auto` setting](#automatic-cluster-membership), however setting -it up yourself allows greater flexability to modify it if `:auto` mode doesn't +it up yourself allows greater flexibility to modify it if `:auto` mode doesn't meet your requirements. diff --git a/lib/horde/distribution_strategy.ex b/lib/horde/distribution_strategy.ex index 8ffe43c8..686c5a08 100644 --- a/lib/horde/distribution_strategy.ex +++ b/lib/horde/distribution_strategy.ex @@ -4,7 +4,7 @@ defmodule Horde.DistributionStrategy do @moduledoc """ Define your own distribution strategy by implementing this behaviour and configuring Horde to use it. - A few distribution stategies are included in Horde, namely: + A few distribution strategies are included in Horde, namely: - `Horde.UniformDistribution` - `Horde.UniformQuorumDistribution` diff --git a/test/registry_test.exs b/test/registry_test.exs index e07a4a6d..15aa369a 100644 --- a/test/registry_test.exs +++ b/test/registry_test.exs @@ -688,7 +688,7 @@ defmodule RegistryTest do :ok = Horde.Registry.put_meta(registry, :custom_key, "custom_value") - assert :error = Horde.Registry.meta(registry, :non_existant) + assert :error = Horde.Registry.meta(registry, :non_existent) end test "meta is propagated" do @@ -825,7 +825,7 @@ defmodule RegistryTest do assert_receive {:unregister, ^reg, :task, ^task_pid}, 200 end - test "recieves :register and :unregister from another node" do + test "receives :register and :unregister from another node" do Process.register(self(), :test_process) reg = start_registry(listeners: [:test_process], keys: :unique) reg2 = start_registry(keys: :unique)