From c60a1173018e93e6bf433f87cb726adc979d1c8a Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Fri, 14 Feb 2020 03:09:01 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/topics/web_application_firewall/index.md | 2 +- doc/topics/web_application_firewall/quick_start_guide.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/topics/web_application_firewall') diff --git a/doc/topics/web_application_firewall/index.md b/doc/topics/web_application_firewall/index.md index db1265e08ac..6c847f12bba 100644 --- a/doc/topics/web_application_firewall/index.md +++ b/doc/topics/web_application_firewall/index.md @@ -55,7 +55,7 @@ you can configure a cluster on GKE. Once this is set up, you can follow the step NOTE: **Note** This guide shows how the WAF can be deployed using Auto DevOps. The WAF -is avaliable by default to all applications no matter how they are deployed, +is available by default to all applications no matter how they are deployed, as long as they are using Ingress. ## Network firewall vs. Web Application Firewall diff --git a/doc/topics/web_application_firewall/quick_start_guide.md b/doc/topics/web_application_firewall/quick_start_guide.md index 35003785753..e3cf0bcd498 100644 --- a/doc/topics/web_application_firewall/quick_start_guide.md +++ b/doc/topics/web_application_firewall/quick_start_guide.md @@ -12,7 +12,7 @@ need to ensure your own [Runners are configured](../../ci/runners/README.md) and [Google OAuth is enabled](../../integration/google.md). **Note**: GitLab's Web Application Firewall is deployed with [Ingress](../../user/clusters/applications.md#Ingress), -so it will be avaliable to your applications no matter how you deploy them to Kubernetes. +so it will be available to your applications no matter how you deploy them to Kubernetes. ## Enable or disable ModSecurity -- cgit v1.2.1