3 files changed, 11 insertions, 11 deletions
diff --git a/docs/customising/config.md b/docs/customising/config.md
index 2528adefc..39ab4cdf7 100644
--- a/docs/customising/config.md
+++ b/docs/customising/config.md
@@ -14,7 +14,7 @@ title: Configuration
 
 The alaveteli code ships with an example configuration file: `config/general.yml-example`.
 
-As part of the [installation process]({{ site.baseurl }}docs/installing ), the
+As part of the [installation process]({{ site.baseurl }}docs/installing/ ), the
 example file gets copied to `config/general.yml`. You **must** edit this file to
 suit your needs.
 
@@ -372,7 +372,7 @@ indentation correct. If in doubt, look at the examples already in the file, and
     <a name="theme_urls"><code>THEME_URLS</code></a>
   </dt>
   <dd>
-    URLs of <a href="{{ site.baseurl }}docs/customising/themes">themes</a> to download and use
+    URLs of <a href="{{ site.baseurl }}docs/customising/themes/">themes</a> to download and use
     (when running the <code>rails-post-deploy</code> script). The earlier in the list means
     the templates have a higher priority.
     <div class="more-info">
@@ -392,7 +392,7 @@ THEME_URLS:
     <a name="theme_branch"><code>THEME_BRANCH</code></a>
   </dt>
   <dd>
-    When <code>rails-post-deploy</code> installs the <a href="{{ site.baseurl }}docs/customising/themes">themes</a>,
+    When <code>rails-post-deploy</code> installs the <a href="{{ site.baseurl }}docs/customising/themes/">themes</a>,
     it will try the theme branch first, but only if you've set <code>THEME_BRANCH</code>
     to be true. If the branch doesn't exist it will fall back to using a tagged version
     specific to your installed alaveteli version, and if that doesn't exist it will
diff --git a/docs/customising/index.md b/docs/customising/index.md
index 4b8cf9fda..19100ad20 100644
--- a/docs/customising/index.md
+++ b/docs/customising/index.md
@@ -15,7 +15,7 @@ title: Customising
 ## Configuration settings
 
 You can customise much of Alaveteli's behaviour just by editing the configuration
-file. This [complete list of Alaveteli's config settings]({{ site.baseurl }}docs/customising/config)
+file. This [complete list of Alaveteli's config settings]({{ site.baseurl }}docs/customising/config/)
 shows the sort of things you can control in this way.
 
 <!-- TODO key settings -->
@@ -24,7 +24,7 @@ shows the sort of things you can control in this way.
 
 It's common to want to change the basic appearance of the site. Although you
 can simply edit the default templates and CSS to do this, we **strongly
-recommend** that you [create a theme]({{ site.baseurl }}docs/customising/themes).
+recommend** that you [create a theme]({{ site.baseurl }}docs/customising/themes/).
 
 Themes do not need to be especially complex, but they allow your changes to
 work alongside the core code, which you can then update (when new releases or
@@ -32,13 +32,13 @@ updates become available).
 
 ## Need Alaveteli in a different language?
 
-No problem! See the [information about translating Alaveteli]({{ site.baseurl }}docs/customising/translation).
+No problem! See the [information about translating Alaveteli]({{ site.baseurl }}docs/customising/translation/).
 
 ## Complex changes
 
 If you are a developer (or you have a team of programmers available) you can
 add any customisation that you want. But it's important to do this without
 breaking the core code, so that you can accept new releases with updates.
-There's more detail in the [page about themes]({{ site.baseurl }}docs/customising/themes).
+There's more detail in the [page about themes]({{ site.baseurl }}docs/customising/themes/).
 
-See also the [documentation for developers]({{ site.baseurl }}docs/developers).
+See also the [documentation for developers]({{ site.baseurl }}docs/developers/).
diff --git a/docs/customising/themes.md b/docs/customising/themes.md
index 65410ece2..1a253d43f 100644
--- a/docs/customising/themes.md
+++ b/docs/customising/themes.md
@@ -13,7 +13,7 @@ title: Themes
 </p>
 
 When you customise your Alaveteli site, there is a lot you can change just
-by editing the [config settings]({{ site.baseurl }}docs/customising/config).
+by editing the [config settings]({{ site.baseurl }}docs/customising/config/).
 But if you want to change the way the site looks, or add more specific
 behaviour, you'll need to make a **theme**.
 
@@ -49,7 +49,7 @@ code.
 We try to encapsulate all site-specific functionality in one of these
 places:
 
-* Site [configuration]({{ site.baseurl }}docs/customising/config)
+* Site [configuration]({{ site.baseurl }}docs/customising/config/)
   (e.g., the name of your site, the available
   languages, and so on &mdash; all in `config/general.yml`)
 * Data (e.g. the public bodies to whom requests should be addressed)
@@ -137,7 +137,7 @@ locale you support.
 ## Customising the request states
 
 As mentioned above, if you can possibly live with the
-[default Alaveteli request statuses]({{ site.baseurl }}docs/running/states),
+[default Alaveteli request statuses]({{ site.baseurl }}docs/running/states/),
 it would be good to do so.  Note that you can set how many days counts
 as "overdue" in the main site config file &mdash;
 see [`REPLY_LATE_AFTER_DAYS`]({{ site.baseurl }}docs/customising/config/#reply_late_after_days).