From 302aaf1457cfa120db292f245a67db21e1a4a5e9 Mon Sep 17 00:00:00 2001
From: "Sarvesh.Patil" <111660124+Light13008@users.noreply.github.com>
Date: Sat, 29 Jul 2023 11:33:50 +0530
Subject: [PATCH] Update app-distribution.md

a typo was corrected, 'webapps' was changed to 'web app'.
---
 site/en/enterprise/app-distribution.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/en/enterprise/app-distribution.md b/site/en/enterprise/app-distribution.md
index 6901688c..1a160586 100644
--- a/site/en/enterprise/app-distribution.md
+++ b/site/en/enterprise/app-distribution.md
@@ -29,7 +29,7 @@ The Chrome Web Store hosts extensions and provides many advantages but some deve
 
 Having an efficient way to publish releases is key to making sure customers are using the latest version of your app, with any bug fixes and new features you’ve released, as soon as possible.
 
-In the case of webapps, developers can immediately push an update and make it available to those users that have the apps installed. This is similar for self-hosted extensions, where developers have full control over their releases and can make them immediately available for admins to update.
+In the case of web apps, developers can immediately push an update and make it available to those users that have the apps installed. This is similar for self-hosted extensions, where developers have full control over their releases and can make them immediately available for admins to update.
 
 Extensions uploaded to the Chrome Web Store have to go through a review process that can take several days. If it doesn’t pass the review process, you need to start the process over again.You can reduce the chances of not passing the review process by pushing a release into private mode early, or publishing a second version of the app (with a different app id) as a beta version, to allow for early testing to make sure that the app will pass review successfully.