diff --git a/_posts/2012-10-20-elixir-v0-7-0-released.markdown b/_posts/2012-10-20-elixir-v0-7-0-released.markdown index e0d34ecfd..16db42d47 100644 --- a/_posts/2012-10-20-elixir-v0-7-0-released.markdown +++ b/_posts/2012-10-20-elixir-v0-7-0-released.markdown @@ -7,7 +7,7 @@ excerpt: Elixir v0.7.0 is released with many improvements! Read on for more info --- -Elixir v0.7.0 was released with bug fixes and many improvements, like a `String` module to handle utf-8 binaries and support to environments and nested dependencies in Mix. +Elixir v0.7.0 was released with bug fixes and many improvements, like a `String` module to handle UTF-8 binaries and support to environments and nested dependencies in Mix. We have also taken important steps into normalizing our APIs. In Erlang, accesses to tuple and lists are one-based and binaries are zero-based, but in Elixir we have normalized all of them to rely on zero-based access. diff --git a/_posts/2013-01-27-elixir-v0-8-0-released.markdown b/_posts/2013-01-27-elixir-v0-8-0-released.markdown index 7df2f3911..84a695b40 100644 --- a/_posts/2013-01-27-elixir-v0-8-0-released.markdown +++ b/_posts/2013-01-27-elixir-v0-8-0-released.markdown @@ -22,7 +22,7 @@ We have written a whole [guide chapter about creating OTP applications, supervis ## Improved Unicode support -Elixir favors the use of utf-8 binaries since its first release. In the latest releases, we took it up a notch by adding Unicode support, built upon the Unicode Standard 6.2.0. Elixir v0.8 takes this even further, adding more convenience functions and better support to named sequences: +Elixir favors the use of UTF-8 binaries since its first release. In the latest releases, we took it up a notch by adding Unicode support, built upon the Unicode Standard 6.2.0. Elixir v0.8 takes this even further, adding more convenience functions and better support to named sequences: ```elixir String.capitalize("fiN") #=> "Fin" diff --git a/crash-course.markdown b/crash-course.markdown index 744449711..7fdbb3b0f 100644 --- a/crash-course.markdown +++ b/crash-course.markdown @@ -825,7 +825,7 @@ end ## Adding Elixir to existing Erlang programs -Elixir compiles into BEAM byte code (via Erlang Abstract Format). This means that Elixir code can be called from Erlang and vice versa, without the need to write any bindings. All Elixir modules start with the `Elixir.` prefix followed by the regular Elixir name. For example, here is how to use the utf-8 aware `String` downcase from Elixir in Erlang: +Elixir compiles into BEAM byte code (via Erlang Abstract Format). This means that Elixir code can be called from Erlang and vice versa, without the need to write any bindings. All Elixir modules start with the `Elixir.` prefix followed by the regular Elixir name. For example, here is how to use the UTF-8 aware `String` downcase from Elixir in Erlang: ```erlang -module(bstring). diff --git a/docs.markdown b/docs.markdown index 98a0ad1f4..b70f675d8 100644 --- a/docs.markdown +++ b/docs.markdown @@ -14,7 +14,7 @@ Choose which version you want documentation for. * [EEx](/docs/stable/eex/) - templating library * [ExUnit](/docs/stable/ex_unit/) - unit test library * [IEx](/docs/stable/iex/) - interactive shell -* [Logger](/docs/stable/logger/) - builtin Logger +* [Logger](/docs/stable/logger/) - built-in Logger * [Mix](/docs/stable/mix/) - build tool #### Master @@ -23,7 +23,7 @@ Choose which version you want documentation for. * [EEx](/docs/master/eex/) - templating library * [ExUnit](/docs/master/ex_unit/) - unit test library * [IEx](/docs/master/iex/) - interactive shell -* [Logger](/docs/master/logger/) - builtin Logger +* [Logger](/docs/master/logger/) - built-in Logger * [Mix](/docs/master/mix/) - build tool

v1.3 (download)

@@ -32,7 +32,7 @@ Choose which version you want documentation for. * [EEx](/docs/v1.3/eex/) - templating library * [ExUnit](/docs/v1.3/ex_unit/) - unit test library * [IEx](/docs/v1.3/iex/) - interactive shell -* [Logger](/docs/v1.3/logger/) - builtin Logger +* [Logger](/docs/v1.3/logger/) - built-in Logger * [Mix](/docs/v1.3/mix/) - build tool

v1.2 (download)

@@ -41,7 +41,7 @@ Choose which version you want documentation for. * [EEx](/docs/v1.2/eex/) - templating library * [ExUnit](/docs/v1.2/ex_unit/) - unit test library * [IEx](/docs/v1.2/iex/) - interactive shell -* [Logger](/docs/v1.2/logger/) - builtin Logger +* [Logger](/docs/v1.2/logger/) - built-in Logger * [Mix](/docs/v1.2/mix/) - build tool

v1.1 (download)

@@ -50,5 +50,5 @@ Choose which version you want documentation for. * [EEx](/docs/v1.1/eex/) - templating library * [ExUnit](/docs/v1.1/ex_unit/) - unit test library * [IEx](/docs/v1.1/iex/) - interactive shell -* [Logger](/docs/v1.1/logger/) - builtin Logger +* [Logger](/docs/v1.1/logger/) - built-in Logger * [Mix](/docs/v1.1/mix/) - build tool diff --git a/getting-started/binaries-strings-and-char-lists.markdown b/getting-started/binaries-strings-and-char-lists.markdown index 14cccfd29..85377a61c 100644 --- a/getting-started/binaries-strings-and-char-lists.markdown +++ b/getting-started/binaries-strings-and-char-lists.markdown @@ -91,7 +91,7 @@ iex> "hełło" <> <<0>> <<104, 101, 197, 130, 197, 130, 111, 0>> ``` -Each number given to a binary is meant to represent a byte and therefore must go up to 255. Binaries allow modifiers to be given to store numbers bigger than 255 or to convert a code point to its utf8 representation: +Each number given to a binary is meant to represent a byte and therefore must go up to 255. Binaries allow modifiers to be given to store numbers bigger than 255 or to convert a code point to its UTF-8 representation: ```iex iex> <<255>> @@ -113,9 +113,9 @@ iex> <<1 :: size(1)>> <<1::size(1)>> iex> <<2 :: size(1)>> # truncated <<0::size(1)>> -iex> is_binary(<< 1 :: size(1)>>) +iex> is_binary(<<1 :: size(1)>>) false -iex> is_bitstring(<< 1 :: size(1)>>) +iex> is_bitstring(<<1 :: size(1)>>) true iex> bit_size(<< 1 :: size(1)>>) 1