Correct heading depth for some index pages. (#30)

Author: freakboy3742

docs/en/tutorial/topics/index.md

@@ -6,10 +6,10 @@ Want to go deeper on specific topics? Here are some additional tutorials that ex
 
 Customize your application's appearance by replacing the default "gray bee" icon.
 
-### [Using the camera](camera-access.md)
+## [Using the camera](camera-access.md)
 
 Use the camera on your mobile or desktop device to take and view a picture from within your application.
 
-### [Testing times](testing.md)
+## [Testing times](testing.md)
 
 How do you ensure that your application works, and stays working? By adding a test suite to your project!

docs/en/tutorial/tutorial-3.md

@@ -321,7 +321,7 @@ The `dist` folder will contain a file named `Hello World-0.0.1.dmg`. If you loca
 
 In this example, we've used the `--adhoc-sign` option - that is, we're signing our application with *ad hoc* credentials - temporary credentials that will only work on your machine. We've done this to keep the tutorial simple. Setting up code signing identities is a little fiddly, and they're only *required* if you're intending to distribute your application to others. If we were publishing a real application for others to use, we would need to specify real credentials.
 
-When you're ready to publish a real application, check out the Briefcase How-To guide on [Setting up a macOS code signing identity](https://briefcase.beeware.org/en/latest/how-to/code-signing/macOS.html).
+When you're ready to publish a real application, check out the Briefcase How-To guide on [Setting up a macOS code signing identity](https://briefcase.beeware.org/en/latest/how-to/code-signing/macOS).
 
 ///
 
@@ -454,7 +454,7 @@ Linking... done
 
 In this example, we're not signing our app. As a result, when you use the installer, you'll get a system warning that the application comes from an unknown developer. We've done this to keep the tutorial simple. Setting up code signing identities is a little fiddly, and they're only *required* if you're intending to distribute your application to others. If we were publishing a real application for others to use, we would need to specify a real signing identity; when that signed app is installed, the system will notify the user that the application is from the known identity associated with the certificate.
 
-When you're ready to publish a real application, check out the Briefcase How-To guide on [Setting up a Windows code signing identity](https://briefcase.beeware.org/en/latest/how-to/code-signing/windows.html).
+When you're ready to publish a real application, check out the Briefcase How-To guide on [Setting up a Windows code signing identity](https://briefcase.beeware.org/en/latest/how-to/code-signing/windows).
 
 Once this step completes, the `dist` folder will contain a file named `Hello_World-0.0.1.msi`. If you double click on this installer to run it, you should go through a familiar Windows installation process. Once this installation completes, there will be a "Hello World" entry in your start menu.
 

docs/en/tutorial/tutorial-5/index.md

@@ -6,6 +6,6 @@ So far, we've been running and testing our application on the desktop. However,
 
 Android applications can be compiled on macOS, Windows or Linux.
 
-### [iOS](iOS.md)
+## [iOS](iOS.md)
 
 iOS applications can only be compiled on macOS.

docs/en/tutorial/tutorial-7.md

@@ -617,7 +617,7 @@ The `-r` option for updating requirements is also honored by the `build` and `ru
 
 Faker is just one example of a third-party Python package - a collection of code that isn't part what Python provides out of the box. These third-party packages are most commonly distributed using the [Python Package Index (PyPI)](https://pypi.org), and installed into your local virtual environment. We've been using `pip` in this tutorial, but there are other options.
 
-On desktop platforms (macOS, Windows, Linux), essentially any package on PyPI package can be installed into your virtual environment, or added to your app's requirements. However, when building an app for mobile or web platforms, [your options are slightly limited](https://briefcase.beeware.org/en/latest/about/faq.html#can-i-use-third-party-python-packages-in-my-app).
+On desktop platforms (macOS, Windows, Linux), essentially any package on PyPI package can be installed into your virtual environment, or added to your app's requirements. However, when building an app for mobile or web platforms, [your options are slightly limited](https://briefcase.beeware.org/en/latest/about/faq#can-i-use-third-party-python-packages-in-my-app).
 
 In short; any *pure Python* package (i.e. any package created from a project written *only* in Python) can be used without difficulty. Some packages, though, are created from projects that contain both Python and other languages (e.g. C, C++, Rust, etc). Code written in those languages needs to be compiled to platform-specific binary modules before it can be used, and those pre-compiled binary modules are only available on specific platforms. Mobile and web platforms have very different requirements than "standard" desktop platforms. At this time, most Python packages don't provide pre-compiled binaries for mobile and web platforms.
 

docs/en/tutorial/tutorial-8.md

@@ -269,5 +269,5 @@ So - where to from here?
 
 - If you'd like to go further, there are some additional [topic tutorials](topics/index.md) that go into detail on specific aspects of application development.
 - If you'd like to know more about how to build complex user interfaces with Toga, you can dive into [Toga's
-documentation](https://toga.beeware.org). Toga also has its own   tutorial [demonstrating how to use various features of the widget   toolkit](https://toga.beeware.org/en/latest/tutorial/index.html).
+documentation](https://toga.beeware.org). Toga also has its own tutorial [demonstrating how to use various features of the widget toolkit](https://toga.beeware.org/en/latest/tutorial).
 - If you'd like to know more about the capabilities of Briefcase, you can dive into [Briefcase's documentation](https://briefcase.beeware.org).