From 44e478fcf8d7ce6032dd9697b69e373103e22125 Mon Sep 17 00:00:00 2001
From: skraft-redhat <57144373+skraft-redhat@users.noreply.github.com>
Date: Thu, 28 Apr 2022 15:05:28 +0200
Subject: [PATCH] Update mlbparks-debugging.adoc

---
 documentation/modules/ROOT/pages/mlbparks-debugging.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/modules/ROOT/pages/mlbparks-debugging.adoc b/documentation/modules/ROOT/pages/mlbparks-debugging.adoc
index 2b38eff2..9b7cec73 100644
--- a/documentation/modules/ROOT/pages/mlbparks-debugging.adoc
+++ b/documentation/modules/ROOT/pages/mlbparks-debugging.adoc
@@ -4,7 +4,7 @@
 [#port_forwading_and_debugging]
 == Background: Port Forwarding and Debugging
 Just as we did before with remote shelling into our pods, we can also set up a port-forward between our local machine
-and our pod. The is useful for operations like connecting to a database running in a pod, viewing an administrative web
+and our pod. This is useful for operations like connecting to a database running in a pod, viewing an administrative web
 interface we don't want to expose to the public, or, in our case, attaching a debugger to the JVM running our application
 server.