From ec4f7bfff4caaab14817ea66119a854ea9a0ff13 Mon Sep 17 00:00:00 2001
From: Jonny Spicer <38098411+jonnyspicer@users.noreply.github.com>
Date: Tue, 9 Mar 2021 20:16:22 +0000
Subject: [PATCH] Update 404.md

Fix typo: CloudFont > CloudFront
---
 content/en/templates/404.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/templates/404.md b/content/en/templates/404.md
index 0916e2299..b7d62ec8f 100644
--- a/content/en/templates/404.md
+++ b/content/en/templates/404.md
@@ -50,7 +50,7 @@ Your 404.html file can be set to load automatically when a visitor enters a mist
 * Apache. You can specify `ErrorDocument 404 /404.html` in an `.htaccess` file in the root of your site.
 * Nginx. You might specify `error_page 404 /404.html;` in your `nginx.conf` file.
 * Amazon AWS S3. When setting a bucket up for static web serving, you can specify the error file from within the S3 GUI.
-* Amazon CloudFont. You can specify the page in the Error Pages section in the CloudFont Console. [Details here](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/custom-error-pages.html)
+* Amazon CloudFront. You can specify the page in the Error Pages section in the CloudFront Console. [Details here](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/custom-error-pages.html)
 * Caddy Server. Using `errors { 404 /404.html }`. [Details here](https://caddyserver.com/docs/errors)
 * Netlify. Add `/* /404.html 404` to `content/_redirects`. [Details Here](https://www.netlify.com/docs/redirects/#custom-404)
 * Azure Static website. You can specify the `Error document path` in the Static website configuration page of the Azure portal. [More details are available in the Static website documentation](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-static-website).