Skip to content

Commit 95a78e0

Browse files
authored
Apply suggestions from code review
1 parent 8c58031 commit 95a78e0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

lib/phoenix/tracker.ex

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,12 +72,12 @@ defmodule Phoenix.Tracker do
7272
7373
## Application Shutdown
7474
75-
When a tracker shuts down, the other nodes do not assume it has been gone
75+
When a tracker shuts down, the other nodes do not assume it is gone
7676
for good. After all, in a distributed system, it is impossible to know if something
7777
is just temporarily unavailable or if it has crashed.
7878
7979
For this reason, when you call `System.stop()` or the Erlang VM receives a
80-
`SIGTERM` - any presences that the local tracker instance has will continue to
80+
`SIGTERM`, any presences that the local tracker instance has will continue to
8181
be seen as present by other trackers in the cluster until the `:down_period`
8282
for the instance has passed.
8383
@@ -292,7 +292,7 @@ defmodule Phoenix.Tracker do
292292
(30s down detection). Note: This must be at least 2x the `broadcast_period`.
293293
* `permdown_on_shutdown` - boolean; whether to immediately call
294294
`graceful_permdown/1` on the tracker during a graceful shutdown. See
295-
'Application Shutdown' section. You can only safely set this point if `Phoenix.Tracker`
295+
'Application Shutdown' section. You can only safely set this if `Phoenix.Tracker`
296296
is mounted at the root of your supervision tree and the strategy is `:one_for_one`.
297297
Default `false`.
298298
* `:permdown_period` - The interval in milliseconds to flag a replica

0 commit comments

Comments
 (0)