Move to main

Author: josevalim

_layouts/getting-started.html

@@ -35,7 +35,7 @@ <h1>{{ page.title }}</h1>
 
   <div id="edit-on-github">
     <span>Is something wrong?</span>
-    <a href="{{ site.github.repository_url }}/edit/master/{{ page.path }}">
+    <a href="{{ site.github.repository_url }}/edit/main/{{ page.path }}">
       Edit this page on GitHub.
     </a>
   </div>

_posts/2012-05-25-elixir-v0-5-0-released.markdown

@@ -29,7 +29,7 @@ One of the goals we have set was to have a good website and documentation before
 
 At the same time, [we were working on pygments support](https://bitbucket.org/birkenfeld/pygments-main/pull-request/57/add-elixir-and-elixir-console-lexers), a [documentation generation tool](https://github.com/elixir-lang/ex_doc) and many others. Soon, GitHub was able to syntax highlight Elixir code and [our API documentation was online](/).
 
-At the same time, people started to gather around #elixir-lang channel on irc.freenode.net (now migrated to #elixir on irc.libera.chat) to [play with Elixir](https://github.com/elixir-lang/elixir/tree/master/lib/mix), [start their](https://github.com/guedes/exdate) [own projects](https://github.com/yrashk/validatex) and [tutorials](https://github.com/alco/elixir/wiki/Erlang-Syntax:-A-Crash-Course).
+At the same time, people started to gather around #elixir-lang channel on irc.freenode.net (now migrated to #elixir on irc.libera.chat) to [play with Elixir](https://github.com/elixir-lang/elixir/tree/main/lib/mix), [start their](https://github.com/guedes/exdate) [own projects](https://github.com/yrashk/validatex) and [tutorials](https://github.com/alco/elixir/wiki/Erlang-Syntax:-A-Crash-Course).
 
 Although the initial release was scheduled to April 2012, the feedback from such early developers forced us to review some design and syntax decisions and were extremely important to shape the language as it is today.
 
@@ -41,7 +41,7 @@ There are still many, many things to do! In the next months, we will continue wo
 
 We will also work on better integration and documentation on building Erlang systems. Erlang ships with the [Open Telecom Platform](https://en.wikipedia.org/wiki/Open_Telecom_Platform) which provides many tools to build distributed applications. In v0.5.0, all these tools are already available but we want to make the build process even simpler.
 
-In parallel, we will improve our [documentation generation tool](https://github.com/elixir-lang/ex_doc) and [build tool](https://github.com/elixir-lang/elixir/tree/master/lib/mix) which will likely be merged into core when they are solid enough.
+In parallel, we will improve our [documentation generation tool](https://github.com/elixir-lang/ex_doc) and [build tool](https://github.com/elixir-lang/elixir/tree/main/lib/mix) which will likely be merged into core when they are solid enough.
 
 Finally, we will continue improving the Standard Library. Although Elixir's goal is to rely on Erlang the most as possible, we also want to provide a small Standard Library which makes better use of Elixir semantics. For the next weeks, we will focus on improving the IO and File manipulation modules. New data types may also appear, for example, ranges come to my mind.
 

_posts/2013-01-27-elixir-v0-8-0-released.markdown

@@ -78,7 +78,7 @@ Elixir v0.8 contains a bit of house cleaning too. We have created [the Path modu
 
 ## The new HashDict
 
-For last but not least, Elixir ships with a [new HashDict implementation](https://github.com/elixir-lang/elixir/blob/master/lib/elixir/lib/hash_dict.ex). In Erlang, there are different key-value store implementations and often you need to pick which one is the best for you based on the average size of the dictionary. Generally speaking, [orddicts](http://www.erlang.org/doc/man/orddict.html) are efficient and fast when you want to hold a handful of items, otherwise you should consider [gb_trees](http://www.erlang.org/doc/man/gb_trees.html) unless you want to hold thousands of items, when then [dict](http://www.erlang.org/doc/man/dict.html) becomes your best option. The fact those implementations do not provide the same API, makes it harder to change your code when you realize another implementation would be better fit.
+For last but not least, Elixir ships with a [new HashDict implementation](https://github.com/elixir-lang/elixir/blob/main/lib/elixir/lib/hash_dict.ex). In Erlang, there are different key-value store implementations and often you need to pick which one is the best for you based on the average size of the dictionary. Generally speaking, [orddicts](http://www.erlang.org/doc/man/orddict.html) are efficient and fast when you want to hold a handful of items, otherwise you should consider [gb_trees](http://www.erlang.org/doc/man/gb_trees.html) unless you want to hold thousands of items, when then [dict](http://www.erlang.org/doc/man/dict.html) becomes your best option. The fact those implementations do not provide the same API, makes it harder to change your code when you realize another implementation would be better fit.
 
 For Elixir, we decided to have a single dictionary implementation that would scale as needed. It would start as a compact representation for a handful of items and expand and rehash accordingly as new items are added or removed, providing fast access and modification times on all ranges. We are glad to say our goals were reached and a new `HashDict` implementation ships with Elixir v0.8.
 

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/main/LICENSE) and is maintained by the Elixir Core team, composed of five members: Aleksei Magusev, Andrea Leopardi, Eric Meadows-Jönsson, Fernando Tapia Rico, 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 May and November 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 [[email protected]](mailto:[email protected]). Our [compatibility and deprecation policies](https://hexdocs.pm/elixir/compatibility-and-deprecations.html#content) are also documented.
 

docs.markdown

@@ -25,12 +25,12 @@ Choose which version you want documentation for.
 
 #### Development
 
-* [Elixir](https://hexdocs.pm/elixir/master/) - standard library
-* [EEx](https://hexdocs.pm/eex/master/) - templating library
-* [ExUnit](https://hexdocs.pm/ex_unit/master/) - unit test library
-* [IEx](https://hexdocs.pm/iex/master/) - interactive shell
-* [Logger](https://hexdocs.pm/logger/master/) - built-in Logger
-* [Mix](https://hexdocs.pm/mix/master/) - build tool
+* [Elixir](https://hexdocs.pm/elixir/main/) - standard library
+* [EEx](https://hexdocs.pm/eex/main/) - templating library
+* [ExUnit](https://hexdocs.pm/ex_unit/main/) - unit test library
+* [IEx](https://hexdocs.pm/iex/main/) - interactive shell
+* [Logger](https://hexdocs.pm/logger/main/) - built-in Logger
+* [Mix](https://hexdocs.pm/mix/main/) - build tool
 
 {% for version in site.data.elixir-versions %}
   {% if version[0] == 'stable' %}

getting-started/mix-otp/introduction-to-mix.markdown

@@ -310,7 +310,7 @@ Or on Windows:
 
 ## Exploring
 
-There is much more to Mix, and we will continue to explore it as we build our project. A [general overview is available on the Mix documentation](https://hexdocs.pm/mix/). Read [the Mix source code here](https://github.com/elixir-lang/elixir/tree/master/lib/mix).
+There is much more to Mix, and we will continue to explore it as we build our project. A [general overview is available on the Mix documentation](https://hexdocs.pm/mix/). Read [the Mix source code here](https://github.com/elixir-lang/elixir/tree/main/lib/mix).
 
 Keep in mind that you can always invoke the help task to list all available tasks:
 

trademarks.markdown

@@ -14,7 +14,7 @@ Anyone can use the Elixir trademarks if that use of the trademark is nominative.
 
 You must not visually combine the Elixir logo with any other images, or change the logo in any way other than ways required by printing restrictions. If you want to create your own visual identity in relation to Elixir, you might use the shape of an unrelated "water drop" as part of your design, as seen in many community projects and initiatives. You must not combine or modify the Elixir logo.
 
-The Elixir logo is [available in our repository](https://github.com/elixir-lang/elixir-lang.github.com/tree/master/logos) in both vertical and horizontal versions.
+The Elixir logo is [available in our repository](https://github.com/elixir-lang/elixir-lang.github.com/tree/main/logos) in both vertical and horizontal versions.
 
 ## Nominative use
 
@@ -44,7 +44,7 @@ All examples listed next must strictly adhere to the terms outlined in the previ
 
   * Usage of the "Elixir" word in book titles, meetups, conferences, and podcasts. You must not use the word to imply uniqueness or endorsement from the Elixir team. "The Elixir book" and "The Elixir podcast" are not permitted. "Elixir in Action", "Thinking Elixir", and "Kraków Elixir User Group" are valid examples already in use today.
 
-  * Usage of the "Elixir" word in the names of freely distributed software and hardware products is allowed when referring to use with or suitability for the Elixir programming language, such as wxElixir, Elixirsense, etc. If the product includes the Elixir programming language itself, then [you must also respect its license](https://github.com/elixir-lang/elixir/blob/master/LICENSE).
+  * Usage of the "Elixir" word in the names of freely distributed software and hardware products is allowed when referring to use with or suitability for the Elixir programming language, such as wxElixir, Elixirsense, etc. If the product includes the Elixir programming language itself, then [you must also respect its license](https://github.com/elixir-lang/elixir/blob/main/LICENSE).
 
 ## Examples of not permitted use