Minor docs updates (#7123)

Author: wojtekmach

lib/elixir/lib/kernel.ex

@@ -3819,7 +3819,7 @@ defmodule Kernel do
 
   ## rescue/catch/after
 
-  Function bodies support `rescue`, `catch` and `after` as `SpecialForms.try/1`
+  Function bodies support `rescue`, `catch` and `after` as `Kernel.SpecialForms.try/1`
   does. The following two functions are equivalent:
 
       def format(value) do

lib/elixir/lib/kernel/special_forms.ex

@@ -4,7 +4,7 @@ defmodule Kernel.SpecialForms do
   cannot be overridden by the developer.
 
   We define them in this module. Some of these forms are lexical (like
-  `alias/2`, `case/2`, etc). The macros `{}` and `<<>>` are also special
+  `alias/2`, `case/2`, etc). The macros `{}/1` and `<<>>/1` are also special
   forms used to define tuple and binary data structures respectively.
 
   This module also documents macros that return information about Elixir's

lib/elixir/pages/Compatibility and Deprecations.md

@@ -73,7 +73,7 @@ Deprecated feature                               | Deprecated in | Replaced by (
 `()` to mean `nil`                               | [v1.5]        | `nil` (v1.0)
 `:as_char_lists` value in `t:Inspect.Opts.t/0` type | [v1.5]     | `:as_charlists` (v1.3)
 `:char_lists` key in `t:Inspect.Opts.t/0` type   | [v1.5]        | `:charlists` (v1.3)
-`char_list/0` type                               | [v1.5]        | `charlist/0` type (v1.3)
+`char_list/0` type                               | [v1.5]        | `t:charlist/0` type (v1.3)
 `@compile {:parse_transform, _}` in `Module`     | [v1.5]        | *None*
 EEx: `<%=` in middle and end expressions         | [v1.5]        | Use `<%` (= is allowed only on start expressions) (v1.0)
 `Access.key/1`                                   | [v1.4]        | `Access.key/2` (v1.3)

lib/logger/lib/logger.ex

@@ -16,8 +16,8 @@ defmodule Logger do
       performant when required but also apply backpressure
       when under stress.
 
-    * Wraps OTP's `error_logger` to prevent it from
-      overflowing.
+    * Wraps OTP's [`:error_logger`](http://erlang.org/doc/man/error_logger.html)
+      to prevent it from overflowing.
 
   Logging is useful for tracking when an event of interest happens in your
   system. For example, it may be helpful to log whenever a user is deleted.
@@ -63,7 +63,7 @@ defmodule Logger do
       application is started, but may be changed during runtime
 
     * Error logger configuration - configuration for the
-      wrapper around OTP's `error_logger`
+      wrapper around OTP's [`:error_logger`](http://erlang.org/doc/man/error_logger.html)
 
   ### Application configuration
 
@@ -145,11 +145,11 @@ defmodule Logger do
   ### Error logger configuration
 
   The following configuration applies to `Logger`'s wrapper around
-  Erlang's `error_logger`. All the configurations below must be set
-  before the `:logger` application starts.
+  OTP's [`:error_logger`](http://erlang.org/doc/man/error_logger.html).
+  All the configurations below must be set before the `:logger` application starts.
 
     * `:handle_otp_reports` - redirects OTP reports to `Logger` so
-      they are formatted in Elixir terms. This uninstalls Erlang's
+      they are formatted in Elixir terms. This uninstalls OTP's
       logger that prints terms to terminal. Defaults to `true`.
 
     * `:handle_sasl_reports` - redirects supervisor, crash and
@@ -163,17 +163,17 @@ defmodule Logger do
       reached, triggers the error logger to discard messages. This
       value must be a positive number that represents the maximum
       number of messages accepted per second. Once above this
-      threshold, the `error_logger` enters discard mode for the
-      remainder of that second. Defaults to 500 messages.
+      threshold, the [`:error_logger`](http://erlang.org/doc/man/error_logger.html)
+      enters discard mode for the remainder of that second. Defaults to 500 messages.
 
-  For example, to configure `Logger` to redirect all `error_logger` messages
-  using a `config/config.exs` file:
+  For example, to configure `Logger` to redirect all [`:error_logger`](http://erlang.org/doc/man/error_logger.html)
+  messages using a `config/config.exs` file:
 
       config :logger,
         handle_otp_reports: true,
         handle_sasl_reports: true
 
-  Furthermore, `Logger` allows messages sent by Erlang's `error_logger`
+  Furthermore, `Logger` allows messages sent by OTP's [`:error_logger`](http://erlang.org/doc/man/error_logger.html)
   to be translated into an Elixir format via translators. Translators
   can be dynamically added at any time with the `add_translator/1`
   and `remove_translator/1` APIs. Check `Logger.Translator` for more
@@ -521,8 +521,8 @@ defmodule Logger do
   ## Options
 
     * `:flush` - when `true`, guarantees all messages currently sent
-      to both Logger and Erlang's `error_logger` are processed before
-      the backend is added
+      to both Logger and OTP's [`:error_logger`](http://erlang.org/doc/man/error_logger.html)
+      are processed before the backend is added
 
   """
   @spec add_backend(atom, keyword) :: Supervisor.on_start_child()
@@ -548,8 +548,8 @@ defmodule Logger do
   ## Options
 
     * `:flush` - when `true`, guarantees all messages currently sent
-      to both Logger and Erlang's `error_logger` are processed before
-      the backend is removed
+      to both Logger and OTP's [`:error_logger`](http://erlang.org/doc/man/error_logger.html)
+      are processed before the backend is removed
 
   """
   @spec remove_backend(atom, keyword) :: :ok | {:error, term}