From 1e958cebefca8a48b9679a6d419f07c776e451cb Mon Sep 17 00:00:00 2001
From: Santino Valenzuela <41457708+valenzsa@users.noreply.github.com>
Date: Sun, 11 Nov 2018 02:54:28 -0500
Subject: [PATCH] Fixes a couple of typos (#22991)

Changed "existance" to "existence".  And added space between "application," and "typically".
---
 guide/english/agile/application-lifecycle-management/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/guide/english/agile/application-lifecycle-management/index.md b/guide/english/agile/application-lifecycle-management/index.md
index 8b0a38e9e5..8e72c5de84 100644
--- a/guide/english/agile/application-lifecycle-management/index.md
+++ b/guide/english/agile/application-lifecycle-management/index.md
@@ -7,11 +7,11 @@ Application Lifecycle Management (ALM), while commonly associated with Software
 
 ALM can be divided into three distinct areas: Governance, Development, and Operations:
 
-Governance: Encompasses all of the decision making and project management for this application, extends over the entire existance of the application.
+Governance: Encompasses all of the decision making and project management for this application, extends over the entire existence of the application.
 
 Development: Process (SDLC) of actually creating the application. For most applications, the development process reappears again several more times in the application’s lifetime, including bug fixes, improvements and new versions.
 
-Operations: Work required to run and manage the application,typically begins shortly before deployment, then runs continuously until application retirement. Overlaps at times with Development.  
+Operations: Work required to run and manage the application, typically begins shortly before deployment, then runs continuously until application retirement. Overlaps at times with Development.  
 
 Tools can be used to manage ALM; some of the more popular options include: