Correcting typo

Author: bhider

docs/solution-guidance/Branding-and-site-provisioning-solutions-for-SharePoint.md

@@ -109,7 +109,7 @@ The state of SharePoint files and content affects how easy it is to apply update
 |uncustomized|An attribute associated with a file that indicates that it hasn't been modified.|More than one copy of a file can point to the same source. This makes it easier for designers to implement changes.|
 |customized|An attribute associated with a file that indicates that it has been modified.|After a file becomes customized, it becomes more difficult to apply broad updates.Be very careful about what you customize. As a general rule, it's better to use the default SharePoint files and functionality than to customize system files or introduce customizations that need to be manually updated.|
 |ghosted|A file with a source that is stored outside the content database.|A pointer in the content database (the ghost of the file) still exists that tells SharePoint to look for the file's source on the server's file system.|
-|unghosted|An uncustomized version of the source file resides in the content database.|Example: The SharePoint 2013 Design Manager creates a sandboxed solution to package branding files. It's never added to the file system of the server, therefore by definition its files are considered ghosted. But, the files it deploys are still in an uncustomized state. |
+|unghosted|An uncustomized version of the source file resides in the content database.|Example: The SharePoint 2013 Design Manager creates a sandboxed solution to package branding files. It's never added to the file system of the server, therefore by definition its files are considered unghosted. But, the files it deploys are still in an uncustomized state. |
 
 **Note**  If a file has been customized, it won't be updated when you install new service packs or the SharePoint Online service is updated.