Merge pull request #5186 from metabase/fix-doc-link

Fix a bunch of broken doc links

docs/administration-guide/05-setting-permissions.md

@@ -20,9 +20,9 @@ You’ll notice that you already have two default groups: Administrators and All
 
 You’ll also see that you’re a member of the **Administrators** group — that’s why you were able to go to the Admin Panel in the first place. So, to make someone an admin of Metabase you just need to add them to this group. Metabase admins can log into the Admin Panel and make changes there, and they always have unrestricted access to all data that you have in your Metabase instance. So be careful who you add to the Administrator group!
 
-The **All Users** group is another special one. Every Metabase user is always a  member of this group, though they can also be a member of as many other groups as you want. We recommend using the All Users group as a way to set default access levels for new Metabase users. If you have [Google single sign-on](09-single-sign-on.md) enabled, new users who join that way will be automatically added to the All Users group. (**Important note:** as we mentioned above, a user is given the *most permissive* setting she has for a given database/schema/table across *all* groups she is in. Because of that, it is important that your All Users group should never have *greater* access for an item than a group for which you're trying to restrict access — otherwise the more permissive setting will win out.)
+The **All Users** group is another special one. Every Metabase user is always a  member of this group, though they can also be a member of as many other groups as you want. We recommend using the All Users group as a way to set default access levels for new Metabase users. If you have [Google single sign-on](10-single-sign-on.md) enabled, new users who join that way will be automatically added to the All Users group. (**Important note:** as we mentioned above, a user is given the *most permissive* setting she has for a given database/schema/table across *all* groups she is in. Because of that, it is important that your All Users group should never have *greater* access for an item than a group for which you're trying to restrict access — otherwise the more permissive setting will win out.)
 
-If you’ve set up the [Slack integration](08-setting-up-slack.md) and enabled [Metabot](../users-guide/10-metabot.md), you’ll also see a special **Metabot** group, which will allow you to restrict which questions your users will be able to access in Slack via Metabot.
+If you’ve set up the [Slack integration](09-setting-up-slack.md) and enabled [Metabot](../users-guide/11-metabot.md), you’ll also see a special **Metabot** group, which will allow you to restrict which questions your users will be able to access in Slack via Metabot.
 
 #### Managing groups
 

docs/administration-guide/06-collections.md

@@ -3,7 +3,7 @@
 
 Collections are a great way to organize your saved questions and decide who gets to see and edit things. Collections could be things like, "Important Metrics," "Marketing KPIs," or "Questions about users." Multiple [user groups](05-setting-permissions.md) can be given access to the same collections, so we don't necessarily recommend naming collections after user groups.
 
-This page will teach you how to create and manage your collections. For more information on organizing saved questions and using collections, [check out this section of the User's Guide](../users-guide/05-sharing-answers.md).
+This page will teach you how to create and manage your collections. For more information on organizing saved questions and using collections, [check out this section of the User's Guide](../users-guide/06-sharing-answers.md).
 
 ### Creating and editing collections
 Only administrators of Metabase can create and edit collections. From the Questions section of Metabase, click on the `Create a collection` button. Give your collection a name, choose a color for it, and give it a description if you'd like.

docs/administration-guide/11-getting-started-guide.md

@@ -10,7 +10,7 @@ Before you've even created your guide, this page gives you some links that you c
 
 ![Sections](images/gsg/sections.png)
 
-You can highlight your company's most important dashboard, [metrics](06-segments-and-metrics.md) that you commonly refer to (and the dimensions by which they're most often grouped), and tables and [segments](06-segments-and-metrics.md) that are useful or interesting. There's also a place to write a little bit more about "gotchas" or caveats with your data that your users should know about before they start exploring things and drawing conclusions. Lastly, you can optionally include an email address for your users to contact in case they're still confused about things.
+You can highlight your company's most important dashboard, [metrics](07-segments-and-metrics.md) that you commonly refer to (and the dimensions by which they're most often grouped), and tables and [segments](07-segments-and-metrics.md) that are useful or interesting. There's also a place to write a little bit more about "gotchas" or caveats with your data that your users should know about before they start exploring things and drawing conclusions. Lastly, you can optionally include an email address for your users to contact in case they're still confused about things.
 
 If you click on a section, it'll expand and let you select the items that you want to include in that section:
 

docs/users-guide/07-dashboards.md

@@ -91,7 +91,7 @@ Some tips:
 
 *  Place the most important saved question cards near the top of the dashboard, and/or make them bigger than the other cards. That will help draw people’s attention to what matters most.
 *  If you have more than 10 cards on a dashboard, think about breaking the dashboard into two separate ones. You don't want to overwhelm people with too much information, and each dashboard should revolve around one theme or topic. Remember — you can make as many dashboards as you want, so you don’t have to cram everything into just one.
-* Consider [adding filters to your dashboard](06-dashboards.md#dashboard-filters) to make them more useful and flexible. For example, instead of your dashboard being full of questions that are restricted to a specific time span, you can make more general questions and use dashboard filters to change the time span you're looking at.
+* Consider [adding filters to your dashboard](07-dashboards.md#dashboard-filters) to make them more useful and flexible. For example, instead of your dashboard being full of questions that are restricted to a specific time span, you can make more general questions and use dashboard filters to change the time span you're looking at.
 
 ---
 

docs/users-guide/08-dashboard-filters.md

@@ -29,7 +29,7 @@ Now we’ve entered a new mode where we’ll need to wire up each card on our da
 So here’s what we’re doing — when we pick a month and year with our new filter, the filter needs to know which field in the card to filter on. For example, if we have a `Total Orders` card, and each order has a `Date Ordered` as well as a `Date Delivered`, we have to pick which of those fields to filter — do we want to see all the orders *placed* in January, or do we want to see all the orders *delivered* in January? So, for each card on our dashboard, we’ll pick a date field to connect to the filter. If one of your cards says there aren’t any valid fields, that just means that card doesn’t contain any fields that match the kind of filter you chose.
 
 #### Filtering SQL-based cards
-Note that if your dashboard includes cards that were created using the SQL/native query editor, you'll need to add a bit of additional markup to the SQL in those cards in order to use a dashboard filter on them. [Using SQL parameters](12-sql-parameters.md)
+Note that if your dashboard includes cards that were created using the SQL/native query editor, you'll need to add a bit of additional markup to the SQL in those cards in order to use a dashboard filter on them. [Using SQL parameters](13-sql-parameters.md)
 
 
 ![Select fields](images/dashboard-filters/04-select-fields.png)

docs/users-guide/10-pulses.md

@@ -12,7 +12,7 @@ First, choose a name for your pulse. This will show up in the email subject line
 ![Giving it a name](images/pulses/02-name-it.png)
 
 ### Pick Your Data
-Before you can create a pulse, you’ll need to have some [saved questions](05-sharing-answers.md). You can choose up to five of them to put into a single pulse. Click the dropdown to see a list of all your saved questions. You can type in the dropdown to help filter and find the question you’re looking for.
+Before you can create a pulse, you’ll need to have some [saved questions](06-sharing-answers.md). You can choose up to five of them to put into a single pulse. Click the dropdown to see a list of all your saved questions. You can type in the dropdown to help filter and find the question you’re looking for.
 
 ![Pick your data](images/pulses/03-pick-your-data.png)
 

docs/users-guide/11-metabot.md

 ## Getting answers in Slack with MetaBot
 
-You can already send data to Slack on  a set schedule via [Pulses](09-pulses.md) but what about when you need an answer right now? Say hello to MetaBot.
+You can already send data to Slack on  a set schedule via [Pulses](10-pulses.md) but what about when you need an answer right now? Say hello to MetaBot.
 
 MetaBot helps add context to conversations you’re having in Slack by letting you insert results from Metabase.
 
@@ -37,7 +37,7 @@ If you don’t have a sense of which questions you want to view in  Slack, you c
 
 ## To review
 
-- [Connect to Slack](09-pulses.md) to start using MetaBot.
+- [Connect to Slack](10-pulses.md) to start using MetaBot.
 - Show data from Metabase in Slack using ```metabot show <question-id>```
 - Search for questions by typing ```metabot show <search-term>```
 - Get a list of questions by typing ```metabot list```

docs/users-guide/12-data-model-reference.md

@@ -22,4 +22,4 @@ In addition to looking at a table's fields, you can also look at its connections
 ---
 
 ## Next: powering up your SQL questions with variables
-Find out [how to use variables in your native SQL queries](12-sql-parameters.md) to create powerful filter widgets and more.
+Find out [how to use variables in your native SQL queries](13-sql-parameters.md) to create powerful filter widgets and more.