Typos (SharePoint#855)

Author: koreyconway

docs/spfx/enterprise-guidance.md

@@ -95,7 +95,7 @@ SharePoint is and have been one of the most successfull enterprise collaboration
 
 ### Enterprise developers
 
-The SharePoint Framework allows **Enterprise developers**, typically a developer that creates application for use within an organization, to extend SharePoint (Online) with new functionality in a structured and supported way. The SharePoint Framework offers everything from the development framework, build pipeline, to the actual deployment and allows the developers in a short time reach out to all Site Collections with new solutions and features, all controlled by the App Catalog. In an enterprise scenarion you also have full control of the CDN locations; external or internal in SharePoint and you can very easy deploy fixes and updates to your whole organization.
+The SharePoint Framework allows **Enterprise developers**, typically a developer that creates application for use within an organization, to extend SharePoint (Online) with new functionality in a structured and supported way. The SharePoint Framework offers everything from the development framework, build pipeline, to the actual deployment and allows the developers in a short time reach out to all Site Collections with new solutions and features, all controlled by the App Catalog. In an enterprise scenario you also have full control of the CDN locations; external or internal in SharePoint and you can very easily deploy fixes and updates to your whole organization.
 
 Within your enterprise administrators and developers jointly should create a *blue print* for how SharePoint Frameworks solutions should be deployed. The blue print should contain details on preferred client side frameworks, CDN locations etc. For more details, see the section below on *Building a plan around SharePoint Framework customizations*.