 
   Tasks are what make Mix extensible.
 
-  Any project can extend Mix behaviour by adding their own tasks. For
-  example, you can add the task below inside your project and it will
-  be available to everyone that uses your project:
+  Projects can extend Mix behaviour by adding their own tasks. For
+  example, adding the task below inside your project will
+  make it available to everyone that uses your project:
 
       defmodule Mix.Tasks.Hello do
         use Mix.Task

  `mix hello`, which is the equivalent to the `Mix.Tasks.Hello`
  we have defined in the `Mix.Task` section.

  Aliases may also be lists, specifying multiple tasks to run
  at once:

      [all: [&hello/1, "deps.get --only #{Mix.env}", "compile"]]



    * `MIX_ARCHIVES` - specifies the directory into which the archives should be installed
    * `MIX_DEBUG` - outputs debug information about each task before running it
    * `MIX_ENV` - specifies which environment should be used. See [Environments](#environments)
    * `MIX_EXS` - changes the full path to the `mix.exs` file
    * `MIX_HOME` - path to mix's home directory, stores configuration files and scripts used by mix
    * `MIX_PATH` - appends extra code paths
