Fix warnings

Author: josevalim

lib/elixir/pages/getting-started/debugging.md

@@ -77,7 +77,7 @@ dbg(Map.put(feature, :in_version, "1.14.0"))
 
 The code above prints this:
 
-```shell
+```text
 [my_file.exs:2: (file)]
 feature #=> %{inspiration: "Rust", name: :dbg}
 [my_file.exs:3: (file)]
@@ -97,7 +97,7 @@ __ENV__.file
 
 This code prints:
 
-```shell
+```text
 [dbg_pipes.exs:5: (file)]
 __ENV__.file #=> "/home/myuser/dbg_pipes.exs"
 |> String.split("/", trim: true) #=> ["home", "myuser", "dbg_pipes.exs"]

lib/elixir/pages/mix-and-otp/config-and-distribution.md

@@ -56,7 +56,7 @@ Now we just need to read this configuration. Open up `lib/kv.ex` and the `start/
 
 Run `iex -S mix` and you will see the following message printed:
 
-```
+```text
 [info] Accepting connections on port 4050
 ```
 
@@ -149,13 +149,13 @@ In other words, we can spawn processes in other nodes, hold to their PIDs, and t
 
 First, let's check that our code is not currently distributed. Start a new node like this:
 
-```
+```console
 $ PORT=4100 iex --sname foo -S mix
 ```
 
 And the other like this:
 
-```
+```console
 $ PORT=4101 iex --sname bar -S mix
 ```
 
@@ -280,7 +280,7 @@ Now, in your `start/2` callback, we will add this to of the `start/2` function:
 
 Now we can start our nodes as:
 
-```shell
+```console
 $ NODES="foo@computer-name,bar@computer-name" PORT=4040 iex --sname foo -S mix
 $ NODES="foo@computer-name,bar@computer-name" PORT=4041 iex --sname bar -S mix
 ```

lib/elixir/pages/mix-and-otp/docs-tests-and-with.md

@@ -414,7 +414,6 @@ defmodule KV.ServerTest do
 end
 ```
 
-
 Run `mix test` and the tests should all pass. However, make sure to terminate any `iex -S mix` session you may have running, as currently tests and development environment are running on the same port (4040). We will address it in the next chapter.
 
 We added three tests, the first one tests most bucket actions, while the other two deal with error cases. Given there is a lot of shared setup across these tests, we used the `setup/2` macro to deal with common boilerplate. The macro receives the same *test context* as tests and starts a client TCP connection per test. It also defines a unique bucket name using the module name and the test name, making sure any space in the test name is replaced by `-`.
@@ -427,4 +426,4 @@ Then, on each test, we pattern matched on the *test context*, extracting the soc
 
 Except back then we matched on all config and, this time around, we matched only on the data we needed.
 
-Let's move to the next chapter. We will finally make our system distributed by adding a tiny bit of configuration and, *spoiler alert*, changing one line of code.
+Let's move to the next chapter. We will finally make our system distributed by adding a tiny bit of configuration and, *spoiler alert*, changing one line of code.

lib/elixir/pages/mix-and-otp/genservers.md

@@ -9,7 +9,7 @@ To wrap up our distributed key-value store, we will implement a feature where a
 
 We will do by adding a new command, called SUBSCRIBE, to be used like this:
 
-```
+```text
 SUBSCRIBE shopping
 milk SET TO 1
 eggs SET TO 10

lib/elixir/pages/mix-and-otp/releases.md

@@ -11,7 +11,7 @@ A release is a self-contained directory that consists of your application code,
 
 To get started, simply run `mix release` while setting `MIX_ENV=prod`:
 
-```
+```console
 $ MIX_ENV=prod mix release
 Compiling 4 files (.ex)
 Generated kv app
@@ -78,11 +78,11 @@ Releases also provide built-in hooks for configuring almost every need of the pr
 
 In this case, we already have specified a `config/runtime.exs` that deals with both `PORT` and `NODES` environment variables. Furthermore, while releases don't accept a `--sname` parameter, they do allow us to set the name via the `RELEASE_NODE` env var. Therefore, we can start two copies of the system by jumping into `_build/prod/rel/kv` and typing this (remember to adjust `@computer-name` to your actual computer name):
 
-```shell
+```console
 $ NODES="foo@computer-name,bar@computer-name" PORT=4040 RELEASE_NODE="foo" bin/kv start_iex
 ```
 
-```shell
+```console
 $ NODES="foo@computer-name,bar@computer-name" PORT=4041 RELEASE_NODE="bar" bin/kv start_iex
 ```
 

lib/elixir/pages/mix-and-otp/supervisor-and-application.md

@@ -7,7 +7,7 @@
 
 In the [previous chapter](agents.md), we used agents to represent our buckets. In the [introduction to mix](introduction-to-mix.md), we specified we would like to name each bucket so we can do the following:
 
-```elixir
+```text
 CREATE shopping
 OK
 
@@ -145,7 +145,7 @@ end
 
 Now run `mix test` and you will see a couple things happening. First of all, you will get a compilation warning:
 
-```
+```text
 Compiling 1 file (.ex)
     warning: function start/2 required by behaviour Application is not implemented (in module KV)
     │
@@ -159,7 +159,7 @@ This warning is telling us that `use Application` actually defines a behaviour,
 
 Then our application does not even boot because the `start/2` function is not actually implemented:
 
-```
+```text
 18:29:39.109 [notice] Application kv exited: exited in: KV.start(:normal, [])
     ** (EXIT) an exception was raised:
         ** (UndefinedFunctionError) function KV.start/2 is undefined or private

lib/elixir/pages/mix-and-otp/task-and-gen-tcp.md

@@ -109,7 +109,7 @@ My particular telnet client can be exited by typing `ctrl + ]`, typing `quit`, a
 
 Once you exit the telnet client, you will likely see an error in the IEx session:
 
-```
+```text
 ** (MatchError) no match of right hand side value: {:error, :closed}
     (kv) lib/kv/server.ex:45: KV.Server.read_line/1
     (kv) lib/kv/server.ex:37: KV.Server.serve/1