Fix some broken links and section names. (#149)

Author: andrewcroome

content/v2.0/app/autoloading.md

@@ -58,7 +58,7 @@ None of the above classes or modules need a require statement before use.
 
 It's worth noting that, thanks to Hanami's [component managment system](/v2.0/app/container-and-components/), the components you write in `app/` don't commonly need to reference their collaborators using Ruby constants - they instead use the Deps mixin to access their dependencies.
 
-If you are adding a class to the `app/` directory that you want to use an autoloaded Ruby constant to reference, it's very likely that you do not want that class to be registered in your app container. To opt out of registration, use the magic comment `# auto_register: false` or one of the alternative methods discussed in "Opting out of the container" in the [containers and components guide](/v2.0/app/container-and-components/).
+If you are adding a class to the `app/` directory that you want to use an autoloaded Ruby constant to reference, it's very likely that you do not want that class to be registered in your app container. To opt out of registration, use the magic comment `# auto_register: false` or one of the alternative methods discussed in "Opting out of the container" in the [container and components guide](/v2.0/app/container-and-components/).
 
 ```ruby
 # auto_register: false

content/v2.0/app/booting.md

@@ -157,4 +157,4 @@ irb(main)> Hanami.app.keys
  "rack.monitor"]
 ```
 
-You can read more about components and containers in more detail in the [Containers and components guide](/v2.0/app/container-and-components/). Providers are covered in the [providers guide](/v2.0/app/providers/).
+You can read more about components and containers in more detail in the [container and components guide](/v2.0/app/container-and-components/). Providers are covered in the [providers guide](/v2.0/app/providers/).

content/v2.0/app/environments.md

@@ -103,4 +103,4 @@ See the [app config guide](/v2.0//app/app-config/) for information on supported
 
 When deploying your application to production, set the `HANAMI_ENV` environment variable to `production`.
 
-In production, Hanami logs to standard out by default, using a structured JSON format with a log level of `:info` rather than `:debug`, which is used in development and test. See the [logger guide](/v2.0/app/logger/) for more detail.
+In production, Hanami logs to standard out by default, using a structured JSON format with a log level of `:info` rather than `:debug`, which is used in development and test. See the [logger guide](/v2.0/logger/configuration/) for more detail.

content/v2.0/app/settings.md

@@ -19,7 +19,7 @@ end
 
 Using this class, you can specify what settings exist within your application, what types and defaults they have, and whether or not they are required for your application to boot.
 
-These "app settings" are unrelated to ["app configs"](/v2.0//app/app-config/), which configure framework behaviours. App settings are your own to define and use.
+These "app settings" are unrelated to ["app configs"](/v2.0/app/app-config/), which configure framework behaviours. App settings are your own to define and use.
 
 Each app setting is read from an environment variable matching its name. For example, the Redis URL and Sentry DSN settings below are sourced from the `REDIS_URL` and `SENTRY_DSN` environment variables respectively.
 

content/v2.0/app/slices.md

@@ -71,7 +71,7 @@ module API
         end
 
         def handle(request, response)
-          response.format = format(:json)
+          response.format = :json
 
           halt 422, {error: "Unprocessable country code"}.to_json unless request.params.valid?
 
@@ -326,7 +326,7 @@ end
 
 Slice settings are loaded from environment variables just like the app settings, so take care to ensure you have no naming clashes between your slice and app settings.
 
-See the [settings guide](/v2.0//app/app-config/) for more information on settings.
+See the [settings guide](/v2.0/app/settings/) for more information on settings.
 
 ## Slice loading
 

content/v2.0/introduction/getting-started.md

@@ -727,7 +727,7 @@ end
 
 To get this spec to pass, we'll need to update our books index action to return books from the books relation.
 
-To access the books relation within the action, we can use Hanami's "Deps mixin". Covered in detail in the [containers and components](/v2.0/app/container-and-components/) section of the Architecture guide, the Deps mixin gives each of your application's components easy access to the other components it depends on to achieve its work. We'll see this in more detail as these guides progress.
+To access the books relation within the action, we can use Hanami's "Deps mixin". Covered in detail in the [container and components](/v2.0/app/container-and-components/) section of the Architecture guide, the Deps mixin gives each of your application's components easy access to the other components it depends on to achieve its work. We'll see this in more detail as these guides progress.
 
 For now however, it's enough to know that we can use `include Deps["persistence.rom"]` to make rom-rb available via a `rom` method within our action. The books relation is then available via `rom.relations[:books]`.