Fix misc typos (#12844)

lib/elixir/lib/calendar/datetime.ex

@@ -72,7 +72,7 @@ defmodule DateTime do
   rules, ultimately affecting the result. For example, a country may
   choose to enter or abandon "Daylight Saving Time", which is a
   process where we adjust the clock one hour forward or one hour
-  back once per year. Whenener the rules change, the exact instant
+  back once per year. Whenever the rules change, the exact instant
   that 2:30 AM in Polish time will be in Brazil may change.
 
   In other words, whenever working with future DateTimes, there is

lib/elixir/lib/kernel/special_forms.ex

@@ -349,7 +349,7 @@ defmodule Kernel.SpecialForms do
 
   Or as a part of function definitions to pattern match:
 
-      defmodule ImageTyper do
+      defmodule ImageType do
         @png_signature <<137::size(8), 80::size(8), 78::size(8), 71::size(8),
                          13::size(8), 10::size(8), 26::size(8), 10::size(8)>>
         @jpg_signature <<255::size(8), 216::size(8)>>

lib/elixir/lib/path.ex

@@ -856,7 +856,7 @@ defmodule Path do
 
     * The path is not relative, such as `"/foo/bar"`.
 
-    * A `..` component would make it so that the path would travers up above
+    * A `..` component would make it so that the path would traverse up above
       the root of `relative_to`.
 
     * A symbolic link in the path points to something above the root of `cwd`.

lib/elixir/lib/task.ex

@@ -1116,7 +1116,7 @@ defmodule Task do
   ## Example
 
   `Task.yield_many/2` allows developers to spawn multiple tasks
-  and retrieve the results received in a given timeframe.
+  and retrieve the results received in a given time frame.
   If we combine it with `Task.shutdown/2` (or `Task.ignore/1`),
   it allows us to gather those results and cancel (or ignore)
   the tasks that have not replied in time.

lib/elixir/pages/anti-patterns/code-anti-patterns.md

@@ -81,7 +81,7 @@ def get_customer(customer_id) do
           {:ok, customer}
 
         {:error, _} ->
-          {:error, "invalid reponse body"}
+          {:error, "invalid response body"}
       end
 
     {:error, %{status: status, body: body}} ->
@@ -90,7 +90,7 @@ def get_customer(customer_id) do
           {:error, message}
 
         %{} ->
-          {:error, "invalid reponse with status #{status}"}
+          {:error, "invalid response with status #{status}"}
       end
   end
 end

lib/elixir/pages/references/syntax-reference.md

@@ -159,7 +159,7 @@ end
 
 ### Sigils
 
-Sigils start with `~` and are followed by one lowercase letter or by one or more uppercase letters, immediatelly followed by one of the following pairs:
+Sigils start with `~` and are followed by one lowercase letter or by one or more uppercase letters, immediately followed by one of the following pairs:
 
   * `(` and `)`
   * `{` and `}`

lib/elixir/pages/references/unicode-syntax.md

@@ -42,7 +42,7 @@ The character must either be all in Cyrillic or all in Latin. The only mixed-scr
 
 Finally, Elixir will also warn on confusable identifiers in the same file. For example, Elixir will emit a warning if you use both variables `а` (Cyrillic) and `а` (Latin) in your code.
 
-That's the overall introduction of how Unicode is used in Elixir identifiers. In a nutshell, its goal is to support different writing systems in use today while keeping the Elixir languague itself clear and secure.
+That's the overall introduction of how Unicode is used in Elixir identifiers. In a nutshell, its goal is to support different writing systems in use today while keeping the Elixir language itself clear and secure.
 
 For the technical details, see the next sections that cover the technical Unicode requirements.
 

lib/iex/lib/iex/info.ex

@@ -2,7 +2,7 @@ defprotocol IEx.Info do
   @fallback_to_any true
 
   @moduledoc """
-  A protocol to print information in IEx about the given datastructure.
+  A protocol to print information in IEx about the given data structure.
 
   `IEx.Helpers.i/1` uses this protocol to display a term-specific list
   of of information.

lib/logger/lib/logger.ex

@@ -457,7 +457,7 @@ defmodule Logger do
   ## Examples
 
   `Logger` will automatically load a default formatter into the default handler
-  on boot. However, you can use this function if you wish to programatically replace
+  on boot. However, you can use this function if you wish to programmatically replace
   a handler formatter. For example, inside tests, you might want to change the formatter
   settings:
 

lib/mix/lib/mix/tasks/cmd.ex

@@ -26,7 +26,7 @@ defmodule Mix.Tasks.Cmd do
 
       $ mix do --app app1 --app app2 cmd pwd
 
-  The tasks aborts whenenever a command exits with a non-zero status.
+  The tasks aborts whenever a command exits with a non-zero status.
 
   This task is automatically re-enabled, so it can be called multiple times
   with different arguments.