Correct use of "who" (#11925)

Author: eksperimental

lib/elixir/lib/application.ex

@@ -552,7 +552,7 @@ defmodule Application do
   Reads the application environment at compilation time from a macro.
 
   Typically, developers will use `compile_env/3`. This function must
-  only be invoked from macros who wish to read the compilation environment
+  only be invoked from macros which aim to read the compilation environment
   dynamically.
 
   It expects a `Macro.Env` as first argument, where the `Macro.Env` is
@@ -597,7 +597,7 @@ defmodule Application do
   or raises.
 
   Typically, developers will use `compile_env!/2`. This function must
-  only be invoked from macros who wish to read the compilation environment
+  only be invoked from macros which aim to read the compilation environment
   dynamically.
 
   It expects a `Macro.Env` as first argument, where the `Macro.Env` is

lib/elixir/lib/task.ex

@@ -195,7 +195,7 @@ defmodule Task do
   This provides more visibility and allows you to control how those tasks are
   terminated when a node shuts down. That might look something like
   `Task.Supervisor.start_child(MySupervisor, task_function)`. This means
-  that, although your code is the one who invokes the task, the actual ancestor of
+  that, although your code is the one invoking the task, the actual ancestor of
   the task is the supervisor, as the supervisor is the one effectively starting it.
 
   To track the relationship between your code and the task, we use the `$callers`