chore: remove unneeded trailing whitespace (#1496)

Author: jbampton

_includes/categories-list.html

@@ -9,7 +9,7 @@ <h3 class="widget-title">Blog Categories</h3>
       <a class="spec" href="/cases.html">{{ category_first }}</a>
     {% else %}
       <a class="spec" href="/blog/categories.html#{{ category_first }}">{{ category_first }}</a>
-    {% endif %}      
+    {% endif %}
     </li>
   {% endfor %}
   </ul>

_includes/pagination.html

@@ -7,7 +7,7 @@
     {% endif %}
   {% endif %}
 
-  
+
   {% if paginator.page == 1 %}
     <span class="page-numbers current">1</span>
   {% else %}

_includes/search.html

@@ -7,7 +7,7 @@ <h3>
 <div class="widget search">
   <form method="post" role="search" id="search-form" class="search-form" action="https://duckduckgo.com/?kg=p" onsubmit="document.getElementById('searchq').value = document.getElementById('searchfield').value + ' site:elixir-lang.org | site:hexdocs.pm/elixir | site:hexdocs.pm/mix | site:hexdocs.pm/eex | site:hexdocs.pm/logger | site:hexdocs.pm/iex | site:hexdocs.pm/ex_unit'; return true;">
 		<input type="hidden" id="searchq" name="q" value="" aria-hidden="true">
-	 
+
     		<input class="search-text" type="search" placeholder="Search..." id="searchfield" aria-label="Search box">
 		<input class="search-submit button" name="submit" type="submit" value="Search" aria-label="Search button">
 	</form>

_layouts/post.html

@@ -16,7 +16,7 @@ <h2>{{ page.subtitle }}</h2>
             <a class="category" href="/cases.html">{{ category }}</a>
           {% else %}
             <a class="category" href="/blog/categories.html#{{ category }}">{{ category }}</a>
-          {% endif %}    
+          {% endif %}
         {% endfor %}</div>
       </div>
 

_posts/2020-08-20-embedded-elixir-at-farmbot.markdown

@@ -31,20 +31,20 @@ Connor says that the Nerves Platform and what eventually became NervesHub was a
 
 ### 1. Nerves supports lean systems and operates well in low-bandwidth areas
 
-Because Nerves bundles entire applications into relatively small archives in terms of firmware images for full Linux systems, Farmbot can use NervesHub to send over-the-air updates more quickly and users can download them faster. For comparison, an Android update generally clocks in at around 4 GB, but a Nerves update can be packed into as little as 12 MB. 
+Because Nerves bundles entire applications into relatively small archives in terms of firmware images for full Linux systems, Farmbot can use NervesHub to send over-the-air updates more quickly and users can download them faster. For comparison, an Android update generally clocks in at around 4 GB, but a Nerves update can be packed into as little as 12 MB.
 
-This is especially helpful for Farmbot users who operate in more remote locations with lower bandwidth and less reliable access to Wi-Fi. When an internet connection is available, NervesHub will connect and check if there's an update, and then prompt the user to install the update. 
+This is especially helpful for Farmbot users who operate in more remote locations with lower bandwidth and less reliable access to Wi-Fi. When an internet connection is available, NervesHub will connect and check if there's an update, and then prompt the user to install the update.
 
 ### 2. Nerves adds convenience with low overhead
 
-For devices that are already connected to the internet, connecting to Nerves requires no additional configuration because NervesHub is compatible with the current public key infrastructure for device-to-cloud communication. Since Farmbot already had internet-connected devices when they brought Nerves onboard, they were able to use the same "key" to sign in to NervesHub that they use for their cloud service. 
+For devices that are already connected to the internet, connecting to Nerves requires no additional configuration because NervesHub is compatible with the current public key infrastructure for device-to-cloud communication. Since Farmbot already had internet-connected devices when they brought Nerves onboard, they were able to use the same "key" to sign in to NervesHub that they use for their cloud service.
 
 ### 3. Nerves has all the benefits of Elixir and Erlang
 
 Because it's written in Elixir and built within the Erlang runtime system, Nerves retains the qualities of that language and framework — notably that they are distributed, fault-tolerant, soft real-time, and highly available. Connor also says that with Nerves, it's easy to reason about the things you build with Nerves because you only input what you need into a Nerves application, helping you to avoid unnecessary complexities or unforeseen security vulnerabilities. You can check up on devices as they're running and debug them without disruption to the user experience.
 
 ## The result
 
-FarmBot now has around 300 devices live in NervesHub, with a different deployment for each of their device models. Nerves is built to scale, so as Farmbot continues to grow its user base and expand their product capabilities, they'll be able to continue developing and releasing reliable firmware updates using Nerves.  
+FarmBot now has around 300 devices live in NervesHub, with a different deployment for each of their device models. Nerves is built to scale, so as Farmbot continues to grow its user base and expand their product capabilities, they'll be able to continue developing and releasing reliable firmware updates using Nerves.
 
 *This case study has first been published on [Nerves' website](https://www.nerves-project.org/customer-farmbot)*.

_posts/2020-09-24-paas-with-elixir-at-Heroku.markdown

@@ -61,7 +61,7 @@ The growth of both Elixir teams has been mostly organic. Given there are multipl
 
 According to Matthew Peck, "the paradigm shift from Object-Oriented languages to Functional Programming was our biggest challenge when first learning Elixir". However, the team agrees the investment was worth it: "Learning Elixir has made us better programmers. We have found that immutability made our code more readable, easier to test, and simpler to make concurrent. Now when we go back to an Object-Oriented language, we are thinking about how we can apply the same concepts there" - said Mike Hagerdon.
 
-Amanda Dolan added some remarks on Elixir's capabilities for writing concurrent and fault-tolerant applications: "One other challenge when learning Elixir is fully grasping concurrency and the Erlang/OTP patterns". Some of them felt it took longer to master those concepts than they first expected. 
+Amanda Dolan added some remarks on Elixir's capabilities for writing concurrent and fault-tolerant applications: "One other challenge when learning Elixir is fully grasping concurrency and the Erlang/OTP patterns". Some of them felt it took longer to master those concepts than they first expected.
 
 Taylor Mock has his take on the challenges teams may face when adopting Elixir: "Another difference between Elixir and our previous stacks, Ruby and Node.js, is in the ecosystems". They were initially concerned that the Elixir ecosystem would lack when it comes to third-party tools, but that was not what they saw. Taylor continues: "We found out that we can get really far with the concepts and mechanisms that the language itself provides. This shift can be scary, but we are now past it, and we find ourselves with leaner applications and fewer dependencies".
 

_posts/2020-10-08-real-time-communication-at-scale-with-elixir-at-discord.markdown

@@ -26,7 +26,7 @@ Discord has also explored other technologies along the way, Go and Rust being tw
 
 ## Communication at scale
 
-Effective communication plays an essential role when handling millions of connected users concurrently. To put things into perspective, some of Discord's most popular servers, such as those dedicated to Fortnite and Minecraft, are nearing six hundred thousand users. At a given moment, it is not unlikely to encounter more than two hundred thousand active users in those servers. If someone changes their username, Discord has to broadcast this change to all connected users. 
+Effective communication plays an essential role when handling millions of connected users concurrently. To put things into perspective, some of Discord's most popular servers, such as those dedicated to Fortnite and Minecraft, are nearing six hundred thousand users. At a given moment, it is not unlikely to encounter more than two hundred thousand active users in those servers. If someone changes their username, Discord has to broadcast this change to all connected users.
 
 Overall, Discord's communication runs at impressive numbers. They have crossed more than 12 million concurrent users across all servers, with more than 26 million WebSocket events to clients per second, and Elixir is powering all of this.
 

_posts/2020-11-17-real-time-collaboration-with-elixir-at-slab.markdown

@@ -29,7 +29,7 @@ The trial went better than expected, and Jason's journey with Slab had officiall
 
 ## Growing with the platform
 
-Shortly after, Slab was in a private beta with a handful of companies as users. For each major feature they had along the way, Elixir and Phoenix provided the building blocks for it. When they implemented real-time comments, they used Phoenix Channels and Phoenix PubSub. The pattern goes on: "for asynchronous processing, we simply use [Elixir tasks](https://hexdocs.pm/elixir/Task.html)". Later on, to track users editing a document and give each a different cursor color, they used [Phoenix Presence](https://hexdocs.pm/phoenix/Phoenix.Presence.html), a tool that no other web framework offers out-of-the-box. 
+Shortly after, Slab was in a private beta with a handful of companies as users. For each major feature they had along the way, Elixir and Phoenix provided the building blocks for it. When they implemented real-time comments, they used Phoenix Channels and Phoenix PubSub. The pattern goes on: "for asynchronous processing, we simply use [Elixir tasks](https://hexdocs.pm/elixir/Task.html)". Later on, to track users editing a document and give each a different cursor color, they used [Phoenix Presence](https://hexdocs.pm/phoenix/Phoenix.Presence.html), a tool that no other web framework offers out-of-the-box.
 
 Another leap in Jason's journey with Slab and Elixir was when he had to learn Erlang/OTP, a group of behaviors that ship as part of Erlang's standard library for building distributed and fault-tolerant applications.
 

atom.xml

@@ -4,7 +4,7 @@ elixir_url: http://elixir-lang.org
 ---
 <?xml version="1.0" encoding="utf-8"?>
 <feed xmlns="http://www.w3.org/2005/Atom">
- 
+
 <title>Elixir Lang</title>
 <link href="{{ page.elixir_url }}/atom.xml" rel="self"/>
 <link href="{{ page.elixir_url }}"/>
@@ -25,5 +25,5 @@ elixir_url: http://elixir-lang.org
   <content type="html">{{ post.content | xml_escape }}</content>
 </entry>
 {% endfor %}
- 
+
 </feed>

development.markdown

@@ -12,7 +12,7 @@ José Valim created Elixir in 2012 as a Research and Development project inside
 
 Elixir runs on top of the Erlang Virtual Machine, which provides a scalable and fault-tolerant foundation. Elixir was designed to leverage this foundation without performance costs and aims to contribute to the wider ecosystem whenever possible.
 
-Elixir's source code is under the [Apache 2 License](https://github.com/elixir-lang/elixir/blob/master/LICENSE) and is maintained by the Elixir Core team, composed of six members: Aleksei Magusev, Andrea Leopardi, Eric Meadows-Jönsson, Fernando Tapia Rico, James Fish, and José Valim. The Elixir team works towards an even understanding of the Elixir codebase across all members so it never depends on a single person. The source code and information for contributors can be found on [the language repository](https://github.com/elixir-lang/elixir). 
+Elixir's source code is under the [Apache 2 License](https://github.com/elixir-lang/elixir/blob/master/LICENSE) and is maintained by the Elixir Core team, composed of six members: Aleksei Magusev, Andrea Leopardi, Eric Meadows-Jönsson, Fernando Tapia Rico, James Fish, and José Valim. The Elixir team works towards an even understanding of the Elixir codebase across all members so it never depends on a single person. The source code and information for contributors can be found on [the language repository](https://github.com/elixir-lang/elixir).
 
 Elixir v1.0 was released in September 2014 and a new minor version is released every 6 months, around January and July of every year. New releases are announced in the read-only [announcements mailing list](https://groups.google.com/group/elixir-lang-ann) with a link to the complete CHANGELOG. All security releases [will be tagged with "[security]"](https://groups.google.com/forum/#!searchin/elixir-lang-ann/%5Bsecurity%5D%7Csort:date). Security vulnerabilities should be disclosed to [elixir-security@googlegroups.com](mailto:elixir-security@googlegroups.com). Our [compatibility and deprecation policies](https://hexdocs.pm/elixir/compatibility-and-deprecations.html#content) are also documented.
 
@@ -21,7 +21,7 @@ Since v1.0, the language development has become focused to provide a compact and
   1. are necessary for developing the language itself
   2. bring important concepts/features to the community in a way its effect can only be maximized or leveraged by making it part of the language
 
-The language development is open, both in terms of source code and of collaborations. All features and bug fixes planned for the next releases can be found [in the issues tracker](https://github.com/elixir-lang/elixir/issues). Features that may cause a larger impact on the ecosystem are first proposed to the community in [the Elixir mailing list](https://groups.google.com/group/elixir-lang-core) as well as in [the "Elixir News" section in the Elixir Forum](https://elixirforum.com/c/elixir-news). 
+The language development is open, both in terms of source code and of collaborations. All features and bug fixes planned for the next releases can be found [in the issues tracker](https://github.com/elixir-lang/elixir/issues). Features that may cause a larger impact on the ecosystem are first proposed to the community in [the Elixir mailing list](https://groups.google.com/group/elixir-lang-core) as well as in [the "Elixir News" section in the Elixir Forum](https://elixirforum.com/c/elixir-news).
 
 Community members are welcome to propose new features for Elixir. Before submitting a proposal, members are encouraged to gather feedback from around the community in whatever venues seem best. However, in order for a proposal to be considered for inclusion by the Elixir Core team, it must go through the Elixir mailing list. This often includes discussion and refinement of the proposal. The Elixir Core team has the final say on whether a proposal is accepted or rejected. While members are encouraged to gain support from the rest of the community, popularity does not mean that a proposal will be accepted.
 

getting-started/alias-require-and-import.markdown

@@ -134,7 +134,7 @@ defmodule AssertionTest do
 end
 ```
 
-Behind the scenes, `use` requires the given module and then calls the `__using__/1` callback on it allowing the module to inject some code into the current context. Some modules (for example, the above `ExUnit.Case`, but also `Supervisor` and `GenServer`) use this mechanism to populate your module with some basic behaviour, which your module is intended to override or complete. 
+Behind the scenes, `use` requires the given module and then calls the `__using__/1` callback on it allowing the module to inject some code into the current context. Some modules (for example, the above `ExUnit.Case`, but also `Supervisor` and `GenServer`) use this mechanism to populate your module with some basic behaviour, which your module is intended to override or complete.
 
 Generally speaking, the following module:
 

getting-started/meta/index.html

@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en">
 	<head>
-	  <title>Quote and unquote - Elixir</title>		
+	  <title>Quote and unquote - Elixir</title>
     <meta http-equiv="refresh" content="0; url=/getting-started/meta/quote-and-unquote.html" />
   </head>
 </html>

getting-started/mix-otp/dependencies-and-umbrella-projects.markdown

@@ -198,7 +198,7 @@ deps_path: "../../deps",
 lockfile: "../../mix.lock",
 ```
 
-Those options mean all dependencies will be checked out to `kv_umbrella/deps`, and they will share the same build, config and lock files. We haven't talked about configuration yet, but from here we can build the intuition that all configuration and dependencies are shared across all projects in an umbrella, and it is not per application. 
+Those options mean all dependencies will be checked out to `kv_umbrella/deps`, and they will share the same build, config and lock files. We haven't talked about configuration yet, but from here we can build the intuition that all configuration and dependencies are shared across all projects in an umbrella, and it is not per application.
 
 The second change is in the `application` function inside `mix.exs`:
 

getting-started/mix-otp/ets.markdown

@@ -29,9 +29,9 @@ iex> :ets.lookup(table, "foo")
 When creating an ETS table, two arguments are required: the table name and a set of options. From the available options, we passed the table type and its access rules. We have chosen the `:set` type, which means that keys cannot be duplicated. We've also set the table's access to `:protected`, meaning only the process that created the table can write to it, but all processes can read from it. The possible access controls:
 
   `:public` — Read/Write available to all processes.
-  
+
   `:protected` — Read available to all processes. Only writable by owner process. This is the default.
-  
+
   `:private` — Read/Write limited to owner process.
 
 Be aware that if your Read/Write call violates the access control, the operation will raise `ArgumentError`. Finally, since `:set` and `:protected` are the default values, we will skip them from now on.

getting-started/module-attributes.markdown

@@ -119,7 +119,7 @@ defmodule Foo do
   Module.register_attribute __MODULE__, :param, accumulate: true
 
   @param :foo
-  @param :bar     
+  @param :bar
   # here @param == [:bar, :foo]
 end
 ```

getting-started/sigils.markdown

@@ -161,7 +161,7 @@ def convert(...)
 
 Elixir offers several sigils to deal with various flavors of times and dates.
 
-### Date 
+### Date
 
 A [%Date{}](https://hexdocs.pm/elixir/Date.html) struct contains the fields `year`, `month`, `day`, and `calendar`. You can create one using the `~D` sigil:
 

getting-started/structs.markdown

@@ -137,7 +137,7 @@ iex> %User{}
 Doing it in reverse order will raise a syntax error:
 
 ```elixir
-iex> defmodule User do                          
+iex> defmodule User do
 ...>   defstruct [name: "John", age: 27, :email]
 ...> end
 ** (SyntaxError) iex:107: syntax error before: email

getting-started/typespecs-and-behaviours.markdown

@@ -29,7 +29,7 @@ You can see all the built-in types provided by Elixir [in the typespecs docs](ht
 
 ### Defining custom types
 
-Defining custom types can help communicate the intention of your code and increase its readability. Custom types can be defined within modules via the `@type` attribute. 
+Defining custom types can help communicate the intention of your code and increase its readability. Custom types can be defined within modules via the `@type` attribute.
 
 A simple example of a custom type implementation is to provide a more descriptive alias of an existing type. For example, defining `year` as a type makes your function specs more descriptive than if they had simply used `integer`:
 
@@ -39,7 +39,7 @@ defmodule Person do
    A 4 digit year, e.g. 1984
    """
    @type year :: integer
-   
+
    @spec current_age(year) :: integer
    def current_age(year_of_birth), do: # implementation
 end
@@ -130,7 +130,7 @@ defmodule Parser do
   Parses a string.
   """
   @callback parse(String.t) :: {:ok, term} | {:error, String.t}
-  
+
   @doc """
   Lists all supported file extensions.
   """
@@ -150,7 +150,7 @@ defmodule JSONParser do
 
   @impl Parser
   def parse(str), do: {:ok, "some json " <> str} # ... parse JSON
-  
+
   @impl Parser
   def extensions, do: ["json"]
 end
@@ -162,7 +162,7 @@ defmodule YAMLParser do
 
   @impl Parser
   def parse(str), do: {:ok, "some yaml " <> str} # ... parse YAML
-  
+
   @impl Parser
   def extensions, do: ["yml"]
 end
@@ -178,7 +178,7 @@ defmodule BADParser do
 
   @impl Parser
   def parse, do: {:ok, "something bad"}
-  
+
   @impl Parser
   def extensions, do: ["bad"]
 end

install.markdown

@@ -56,7 +56,7 @@ If your distribution contains an old Elixir/Erlang version, see the sections bel
 
   - **Slackware**
     * Using **Sbopkg**:
-      * Run: `sbopkg -ki "erlang-otp elixir"`  
+      * Run: `sbopkg -ki "erlang-otp elixir"`
     * **Manually**:
       * Download, build and install from SlackBuilds.org: [`erlang-otp`](https://slackbuilds.org/repository/14.2/development/erlang-otp/), and [`elixir`](https://slackbuilds.org/repository/14.2/development/elixir)