Replace quotation marks (#8505)

Replaces "’" U+2019 RIGHT SINGLE QUOTATION MARK with
"'" U+0027 APOSTROPHE.

Replaces “ (U+201C LEFT DOUBLE QUOTATION MARK)
with " (U+0022 QUOTATION MARK).

Author: eksperimental

lib/elixir/lib/file.ex

@@ -528,7 +528,7 @@ defmodule File do
   Updates modification time (mtime) and access time (atime) of
   the given file.
 
-  The file is created if it doesn’t exist. Requires datetime in UTC
+  The file is created if it doesn't exist. Requires datetime in UTC
   (as returned by `:erlang.universaltime()`) or an integer
   representing the POSIX timestamp (as returned by `System.os_time(:second)`).
 
@@ -566,7 +566,7 @@ defmodule File do
   Same as `touch/2` but raises a `File.Error` exception if it fails.
   Returns `:ok` otherwise.
 
-  The file is created if it doesn’t exist. Requires datetime in UTC
+  The file is created if it doesn't exist. Requires datetime in UTC
   (as returned by `:erlang.universaltime()`) or an integer
   representing the POSIX timestamp (as returned by `System.os_time(:second)`).
 

lib/elixir/lib/supervisor.ex

@@ -97,7 +97,7 @@ defmodule Supervisor do
   Supervisors support different strategies; in the example above, we
   have chosen `:one_for_one`. Furthermore, each supervisor can have many
   workers and/or supervisors as children, with each one having its own
-  configuration (as outlined in the “Child specification” section).
+  configuration (as outlined in the "Child specification" section).
 
   The rest of this document will cover how child processes are started,
   how they can be specified, different supervision strategies and more.

lib/elixir/pages/Library Guidelines.md

@@ -192,7 +192,7 @@ Although the previous section could be summarized as "avoid macros", both topics
 
 To quote [the official guide on Macros](https://elixir-lang.org/getting-started/meta/macros.html):
 
-> Even though Elixir attempts its best to provide a safe environment for macros, the major responsibility of writing clean code with macros falls on developers. Macros are harder to write than ordinary Elixir functions and it’s considered to be bad style to use them when they’re not necessary. So write macros responsibly.
+> Even though Elixir attempts its best to provide a safe environment for macros, the major responsibility of writing clean code with macros falls on developers. Macros are harder to write than ordinary Elixir functions and it's considered to be bad style to use them when they're not necessary. So write macros responsibly.
 >
 > Elixir already provides mechanisms to write your everyday code in a simple and readable fashion by using its data structures and functions. Macros should only be used as a last resort. Remember that **explicit is better than implicit**. **Clear code is better than concise code**.
 

lib/elixir/pages/Operators.md

@@ -61,7 +61,7 @@ iex> 1 < :an_atom
 true
 ```
 
-The reason we can compare different data types is pragmatism. Sorting algorithms don’t need to worry about different data types in order to sort. For reference, the overall sorting order is defined below:
+The reason we can compare different data types is pragmatism. Sorting algorithms don't need to worry about different data types in order to sort. For reference, the overall sorting order is defined below:
 
 ```
 number < atom < reference < function < port < pid < tuple < map < list < bitstring