Absolute links

bellkev · bellkev · commit 7ec0de730845 · 2016-06-21T10:55:12.000-07:00
diff --git a/jekyll/_docs/test-metadata.md b/jekyll/_docs/test-metadata.md
@@ -9,7 +9,7 @@ CircleCI can collect test metadata from JUnit XML files and Cucumber JSON files.
 We'll use the test metadata to give you better insight into your build. For our
 inferred steps that use parallelism, we'll always use the timing information to get you
 better test splits and finish your builds faster. You can also take advantage
-of this runtime-based test splitting in custom steps if you follow [these steps](#using-the-files-modifier).
+of this runtime-based test splitting in custom steps if you follow [these steps]({{site.baseurl}}/test-metadata/#using-the-files-modifier).
 
 ## Automatic test metadata collection
 
@@ -125,7 +125,7 @@ You can use [test2junit](https://github.com/ruedigergad/test2junit) to convert C
 ## Using the `files` modifier
 
 If you are collecting test metadata for a custom build step as documented above, you can
-still use runtime-based test splitting with the `files` [modifier](/docs/configuration/#modifiers).
+still use runtime-based test splitting with the `files` [modifier]({{site.baseurl}}/configuration/#modifiers).
 This modifier lets will pass a list of filename arguments to the end of your custom command
 which can be used by your test runner to run a subset of test files on each build node.
 If the "file" attribute is populated in the junit-formatted XML metadata for these
