Fix ordered list formatting

The rules are similar to those for the unordered lists (see previous
commits). Subsequent lines and paragraphs should be aligned to the
beginning of the sentence on the first line, like this:

  1. This is a list item,
     it has a second line.

     Also paragraph.

  2. Second list item.

         code fragment

Short, one-sentence items that can be read as part of the surrounding
paragraph can start with a non-capital letter

Author: alco

lib/eex/lib/eex.ex

@@ -14,20 +14,20 @@ defmodule EEx do
 
   This module provides 3 main APIs for you to use:
 
-  1) Evaluate a string (`eval_string`) or a file (`eval_file`)
-     directly. This is the simplest API to use but also the
-     slowest, since the code is evaluated and not compiled before;
-
-  2) Define a function from a string (`function_from_string`)
-     or a file (`function_from_file`). This allows you to embed
-     the template as a function inside a module which will then
-     be compiled. This is the preferred API if you have access
-     to the template at compilation time;
-
-  3) Compile a string (`compile_string`) or a file (`compile_file`)
-     into Elixir syntax tree. This is the API used by both functions
-     above and is available to you if you want to provide your own
-     ways of handling the compiled template.
+    1. Evaluate a string (`eval_string`) or a file (`eval_file`)
+       directly. This is the simplest API to use but also the
+       slowest, since the code is evaluated and not compiled before.
+
+    2. Define a function from a string (`function_from_string`)
+       or a file (`function_from_file`). This allows you to embed
+       the template as a function inside a module which will then
+       be compiled. This is the preferred API if you have access
+       to the template at compilation time.
+
+    3. Compile a string (`compile_string`) or a file (`compile_file`)
+       into Elixir syntax tree. This is the API used by both functions
+       above and is available to you if you want to provide your own
+       ways of handling the compiled template.
 
   ## Options
 

lib/elixir/lib/kernel/special_forms.ex

@@ -1327,21 +1327,21 @@ defmodule Kernel.SpecialForms do
 
   On the other hand, aliases holds some properties:
 
-  1) The head element of aliases can be any term;
+    1. The head element of aliases can be any term.
 
-  2) The tail elements of aliases are guaranteed to always be atoms;
+    2. The tail elements of aliases are guaranteed to always be atoms.
 
-  3) When the head element of aliases is the atom `:Elixir`, no expansion happen;
+    3. When the head element of aliases is the atom `:Elixir`, no expansion happen.
 
-  4) When the head element of aliases is not an atom, it is expanded at runtime:
+    4. When the head element of aliases is not an atom, it is expanded at runtime:
 
-        quote do: some_var.Foo
-        {:__aliases__, [], [{:some_var, [], Elixir}, :Foo]}
+           quote do: some_var.Foo
+           {:__aliases__, [], [{:some_var, [], Elixir}, :Foo]}
 
-     Since `some_var` is not available at compilation time, the compiler
-     expands such expression to:
+       Since `some_var` is not available at compilation time, the compiler
+       expands such expression to:
 
-        Module.concat [some_var, Foo]
+           Module.concat [some_var, Foo]
 
   """
   defmacro __aliases__(args)

lib/elixir/lib/process.ex

@@ -76,18 +76,18 @@ defmodule Process do
 
   The following behaviour applies if reason is any term except `:normal` or `:kill`:
 
-  1) If pid is not trapping exits, pid will exit with the given reason;
+    1. If pid is not trapping exits, pid will exit with the given reason.
 
-  2) If pid is trapping exits, the exit signal is transformed into a message
-     {:EXIT, from, reason} and delivered to the message queue of pid;
+    2. If pid is trapping exits, the exit signal is transformed into a message
+       {:EXIT, from, reason} and delivered to the message queue of pid.
 
-  3) If reason is the atom `:normal`, pid will not exit. If it is trapping exits,
-     the exit signal is transformed into a message {:EXIT, from, :normal} and
-     delivered to its message queue;
+    3. If reason is the atom `:normal`, pid will not exit. If it is trapping
+       exits, the exit signal is transformed into a message {:EXIT, from,
+       :normal} and delivered to its message queue.
 
-  4) If reason is the atom `:kill`, that is if `exit(pid, :kill)` is called, an
-     untrappable exit signal is sent to pid which will unconditionally exit with
-     exit reason `:killed`.
+    4. If reason is the atom `:kill`, that is if `exit(pid, :kill)` is called,
+       an untrappable exit signal is sent to pid which will unconditionally
+       exit with exit reason `:killed`.
 
   Inlined by the compiler.
 

lib/elixir/lib/record.ex

@@ -14,8 +14,8 @@ defmodule Record do
 
   In Elixir, records are used mostly in two situations:
 
-  1. To work with short, internal data;
-  2. To interface with Erlang records;
+    1. to work with short, internal data
+    2. to interface with Erlang records
 
   The macros `defrecord/3` and `defrecordp/3` can be used to create
   records while `extract/2` can be used to extract records from Erlang

lib/elixir/lib/supervisor/spec.ex

@@ -40,15 +40,15 @@ defmodule Supervisor.Spec do
 
   Explicit supervisors as above are required when there is a need to:
 
-  1. partialy change the supervision tree during hot-code swaps;
+    1. Partialy change the supervision tree during hot-code swaps.
 
-  2. define supervisors inside other supervisors;
+    2. Define supervisors inside other supervisors.
 
-  3. perform actions inside the supervision `init/1` callback.
+    3. Perform actions inside the supervision `init/1` callback.
 
-     For example, you may want to start an ETS table that is linked to
-     the supervisor (i.e. if the supervision tree needs to be restarted,
-     the ETS table must be restarted too);
+       For example, you may want to start an ETS table that is linked to
+       the supervisor (i.e. if the supervision tree needs to be restarted,
+       the ETS table must be restarted too).
 
   ## Supervisor and worker options
 

lib/elixir/lib/system.ex

@@ -153,11 +153,11 @@ defmodule System do
   Returns a writable temporary directory.
   Searches for directories in the following order:
 
-  1. The directory named by the TMPDIR environment variable
-  2. The directory named by the TEMP environment variable
-  3. The directory named by the TMP environment variable
-  4. `C:\TMP` on Windows or `/tmp` on Unix
-  5.  As a last resort, the current working directory
+    1. the directory named by the TMPDIR environment variable
+    2. the directory named by the TEMP environment variable
+    3. the directory named by the TMP environment variable
+    4. `C:\TMP` on Windows or `/tmp` on Unix
+    5. as a last resort, the current working directory
 
   Returns `nil` if none of the above are writable.
   """

lib/mix/lib/mix/compilers/erlang.ex

@@ -24,14 +24,17 @@ defmodule Mix.Compilers.Erlang do
 
   The command above will:
 
-  1. Look for files ending with the `lfe` extension in `src`
-     and their `beam` counterpart in `ebin`;
-  2. For each stale file (or for all if `force` is true),
-     invoke the callback passing the calculated input
-     and output;
-  3. Update the manifest with the newly compiled outputs;
-  4. Remove any output in the manifest that that does not
-     have an equivalent source;
+    1. look for files ending with the `lfe` extension in `src`
+       and their `beam` counterpart in `ebin`
+
+    2. for each stale file (or for all if `force` is true),
+       invoke the callback passing the calculated input
+       and output
+
+    3. update the manifest with the newly compiled outputs
+
+    4. remove any output in the manifest that that does not
+       have an equivalent source
 
   The callback must return `{:ok, mod}` or `:error` in case
   of error. An error is raised at the end if any of the