diff --git a/articles/testing/continuous-integration-circle.md b/articles/testing/continuous-integration-circle.md
index d898849..b2f479b 100644
--- a/articles/testing/continuous-integration-circle.md
+++ b/articles/testing/continuous-integration-circle.md
@@ -72,23 +72,18 @@ When running `prism conduct` you can:
 * Include the Scenario JSON on your CI server, and pass in its absolute file path
 * Pass in the absolute URL to the scenario JSON served up via HTTP
 
-<!-- theme: warning -->
-
 > Don't forget to pass in any required environment values with the --env command
 > line flag (or you can provide the filepath to a json file with your environment
 > variables)!
 
-<!-- theme: info -->
-
 > Did you know? You can find the full command to run your scenario collection
 > or individual scenarios in the Stoplight application. Click on the "Home"
 > button of a scenario under "Trigger This Collection".
 
 ---
 
-**Related**
-
-* [Continuous Integration Overview](./continuous-integration.md)
-* [Continuous Integration with Travis CI](./continous-integration-travis)
-* [Continuous Integration with Jenkins](./continous-integration-jenkins)
-* [Prism Docker Image](https://hub.docker.com/r/stoplight/prism/)
+**Related Articles**
+- [Integrating in Continuous Integration](/testing/continuous-integration/overview)
+- [Integrating with Jenkins](/testing/continuous-integration/jenkins)
+- [Integrating with Travis](/testing/continuous-integration/travis)
+- [Prism Docker Image](https://hub.docker.com/r/stoplight/prism/)