From a0799c5f41ec2d7c9345a79722aa5be41c7b09bf Mon Sep 17 00:00:00 2001
From: Ruben R <7413098+rruizt@users.noreply.github.com>
Date: Tue, 5 May 2020 10:29:13 +0200
Subject: [PATCH] Fix typo

---
 .../asciidoc/security-openid-connect-web-authentication.adoc    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/main/asciidoc/security-openid-connect-web-authentication.adoc b/docs/src/main/asciidoc/security-openid-connect-web-authentication.adoc
index e25e1fd49c86b..2c8c39b1eb393 100644
--- a/docs/src/main/asciidoc/security-openid-connect-web-authentication.adoc
+++ b/docs/src/main/asciidoc/security-openid-connect-web-authentication.adoc
@@ -12,7 +12,7 @@ This guide demonstrates how to use the OpenID Connect Extension to protect your
 The extension allows you to easily enable authentication to your web application based on the Authorization Code Flow so that your users are redirected to a
 OpenID Connect Provider (e.g.: Keycloak) to authenticate and, once the authentication is complete, return back to your application.
 
-We are going to give you a guideline on how to use OpenId Connect to authenticate users using the Quarkus OpenID Connect Extenson.
+We are going to give you a guideline on how to use OpenId Connect to authenticate users using the Quarkus OpenID Connect Extension.
 
 == Prerequisites