diff --git a/docs/environment/custom-domains.md b/docs/environment/custom-domains.md
index 221e81535..bd41478b8 100644
--- a/docs/environment/custom-domains.md
+++ b/docs/environment/custom-domains.md
@@ -50,6 +50,6 @@ After waiting for the DNS change to propagate (sometimes up to several hours) yo
 Some applications serve static files hosted on AWS S3. You can read the [Websites](/docs/websites.md) documentation to learn more.
 
 If you want to host a fully static website with HTML files or a Single Page Application (eg. built with Vue, React or Angular)
-you may be interested in [the Static Website construct of the Lift plugin](https://github.com/getlift/lift/blob/master/docs/static-website.md).
+you may be interested in <a href="https://github.com/getlift/lift/blob/master/docs/static-website.md">the Static Website construct of the Lift plugin</a>.
 
-This allows to configure custom domains, root domain to `www` redirects and more. Check out [the official documentation](https://github.com/getlift/lift/blob/master/docs/static-website.md) for more details.
+This allows to configure custom domains, root domain to `www` redirects and more. Check out <a href="https://github.com/getlift/lift/blob/master/docs/static-website.md">the official documentation</a> for more details.
diff --git a/docs/frameworks/laravel.md b/docs/frameworks/laravel.md
index 9b2ebb381..227c2b1a3 100644
--- a/docs/frameworks/laravel.md
+++ b/docs/frameworks/laravel.md
@@ -89,12 +89,12 @@ For more details follow [the "Console" guide](/docs/runtimes/console.md).
 ## Assets
 
 To deploy Laravel websites, assets need to be served from AWS S3. The easiest approach is to use the
-[Server-side website construct of the Lift plugin](https://github.com/getlift/lift/blob/master/docs/server-side-website.md).
+<a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md">Server-side website construct of the Lift plugin</a>.
 
 This will deploy a Cloudfront distribution that will act as a proxy: it will serve
 static files directly from S3 and will forward everything else to Lambda. This is very close
 to how traditional web servers like Apache or Nginx work, which means your application doesn't need to change!
-For more details, see [the offical documentation](https://github.com/getlift/lift/blob/master/docs/server-side-website.md#how-it-works).
+For more details, see <a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md#how-it-works">the official documentation</a>.
 
 First install the plugin
 
@@ -139,7 +139,7 @@ Now deploy your website using `serverless deploy`. Lift will create all required
 uploading your assets to S3 automatically.
 
 For more details, see the [Websites section](/docs/websites.md) of this documentation
-and the official [Lift documentation](https://github.com/getlift/lift/blob/master/docs/server-side-website.md).
+and the official <a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md">Lift documentation</a>.
 
 ### Assets in templates
 
diff --git a/docs/frameworks/symfony.md b/docs/frameworks/symfony.md
index b88d7849b..fccc67412 100644
--- a/docs/frameworks/symfony.md
+++ b/docs/frameworks/symfony.md
@@ -139,12 +139,12 @@ in `trusted_proxies`.
 ## Assets
 
 To deploy Symfony websites, assets need to be served from AWS S3. The easiest approach is to use the
-[Server-side website construct of the Lift plugin](https://github.com/getlift/lift/blob/master/docs/server-side-website.md).
+<a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md">Server-side website construct of the Lift plugin</a>.
 
 This will deploy a Cloudfront distribution that will act as a proxy: it will serve
 static files directly from S3 and will forward everything else to Lambda. This is very close
 to how traditional web servers like Apache or Nginx work, which means your application doesn't need to change!
-For more details, see [the offical documentation](https://github.com/getlift/lift/blob/master/docs/server-side-website.md#how-it-works). 
+For more details, see <a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md#how-it-works">the official documentation</a>. 
 
 First install the plugin
 
@@ -203,7 +203,7 @@ upload all specified files and directories to the bucket.
 > If you are not using Flex, update the `serverless.yml` file to exclude assets from the deployment ([see the recipe](https://github.com/symfony/recipes-contrib/blob/master/bref/symfony-bridge/0.1/serverless.yaml#L35))
 
 For more details, see the [Websites section](/docs/websites.md) of this documentation 
-and the official [Lift documentation](https://github.com/getlift/lift/blob/master/docs/server-side-website.md).
+and the official <a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md">Lift documentation</a>.
 
 ### Assets in templates