From 90f553abf154c6bffeb360d93d846a917ef55f9c Mon Sep 17 00:00:00 2001 From: Alexander Skiba Date: Sat, 16 Apr 2016 04:24:52 +0700 Subject: [PATCH] Fix typo in ets.markdown --- getting-started/mix-otp/ets.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/getting-started/mix-otp/ets.markdown b/getting-started/mix-otp/ets.markdown index f58d8f0e4..61436b081 100644 --- a/getting-started/mix-otp/ets.markdown +++ b/getting-started/mix-otp/ets.markdown @@ -226,7 +226,7 @@ According to the failure message, we are expecting that the bucket no longer exi Unfortunately this time we cannot simply change `handle_info/2`, the operation responsible for cleaning the ETS table, to a synchronous operation. Instead we need to find a way to guarantee the registry has processed the `:DOWN` notification sent when the bucket crashed. -An easy way to do so is by sending a synchronous request to the registry: because messages are processed in order, if the registry replies to a request sent after the `Agent.stop` call, it means it the `:DOWN` message has been processed. Let's do so by creating a "bogus" bucket, which is a synchronous request, after `Agent.stop` in both tests: +An easy way to do so is by sending a synchronous request to the registry: because messages are processed in order, if the registry replies to a request sent after the `Agent.stop` call, it means that the `:DOWN` message has been processed. Let's do so by creating a "bogus" bucket, which is a synchronous request, after `Agent.stop` in both tests: ```elixir