fix: urls to external

Signed-off-by: Felipe Zipitria <[email protected]>
coreruleset · Apr 27, 2024 · 840ce9c · 840ce9c
1 parent ba0e067
commit 840ce9c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/content/blog/2018-06-19-the-core-rule-set-as-part-of-devops-ci-pipeline.md b/content/blog/2018-06-19-the-core-rule-set-as-part-of-devops-ci-pipeline.md
@@ -43,7 +43,7 @@ This way, the application's traffic is tested with the CRS and we don't have to
 
 ### CRS Docker Container
 
-As you can read at {{< ref "/docs/deployment/install" >}}, it only takes a few steps to install the Core Rule Set. And it gets even easier if you use it in a Docker Container.
+As you can read [here](/docs/deployment/install), it only takes a few steps to install the Core Rule Set. And it gets even easier if you use it in a Docker Container.
 
 I have created a Docker Image that inherits from the official OWASP ModSecurity Core Rule Set Container (<https://hub.docker.com/r/owasp/modsecurity-crs/>). My image adds an Apache reverse proxy configuration. The reverse proxy configuration is used to put the CRS in front of an application. It also adds some more CRS variables. The CRS container can be found at <https://hub.docker.com/r/franbuehler/modsecurity-crs-rp/>. This way, the CRS can be very quickly and easily integrated into automated tests.
 

diff --git a/content/blog/2018-07-26-crs-project-news-july-2018.md b/content/blog/2018-07-26-crs-project-news-july-2018.md
@@ -16,7 +16,7 @@ So here we go for the CRS project newsletter for July 2018:
 
 ## What has happened in recent weeks
 
-- We met for the first CRS community summit in London on July 4, 2018 and then for an on-site developer meeting on Friday July 6. There is a [blog post covering the Summit (and a photo below)]({{< ref "blog/2018-07-12-reporting-from-the-first-crs-community-summit-in-london.md"> }}).
+- We met for the first CRS community summit in London on July 4, 2018 and then for an on-site developer meeting on Friday July 6. There is a [blog post covering the Summit (and a photo below)]({{< ref "blog/2018-07-12-reporting-from-the-first-crs-community-summit-in-london.md" >}}).
 - The dev meeting (replacing the monthly chat for July) was very productive. Below is a list of decisions taken.
 - Chaim Sanders has been named release manager for 3.1. We are aiming for CRS 3.1 in September with a release candidate in August. CRS 3.2 should be ready in early Summer 2019.
 - We're launching the monthly newsletter anew. It's going to be edited by Christian Folini. This is going to be published via the website.