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 typos #257

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)
4 changes: 2 additions & 2 deletions guides/libcluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
2 changes: 1 addition & 1 deletion lib/horde/distribution_strategy.ex
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Expand Down
4 changes: 2 additions & 2 deletions test/registry_test.exs
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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)
Expand Down