Merge pull request #5161 from CarlosNihelton/patch-1

Fix typo in app-capability-declarations.md

Author: drewbatgit

uwp/packaging/app-capability-declarations.md

@@ -261,7 +261,7 @@ The following table lists the restricted capabilities. You may request approval
 | **Package Write Redirection Compatibility Shim** | The **packageWriteRedirectionCompatibilityShim** restricted capability configures your application to create all new files in a per-user location. Any preexisting files opened for writes are first copied into a per-user location and modifications happen to the file in that location. This capability is useful for applications that create or modify files in their installation folder.<br/><br/>This capability is designed for certain types of desktop PC games that are published by Microsoft and our partners. However, it might also be applicable to other apps in some cases. |
 | **Custom Install Actions** | The **customInstallActions** restricted capability enables your application to declare the [windows.customInstall](/uwp/schemas/appxpackage/uapmanifestschema/element-desktop6-package-extension) extension in its package manifest so that it can specify one or more additional installer files (.exe or .msi) that are executed with your application. This allows you to specify custom actions for any of the standard deployment scenarios: install, update, repair, or uninstall. For example, this is useful for applications that bundle a 3rd party redistributable component.<br/><br/>This capability is designed for certain types of desktop PC games that are published by Microsoft and our partners. It will not be granted for other scenarios. |
 | **Packaged Services** | The **packagedServices** restricted capability allows applications that are created by Microsoft partners and enterprises to declare the [windows.service](/uwp/schemas/appxpackage/uapmanifestschema/element-desktop6-extension) extension in its package manifest so that it can install one or more services along with the app. These services can be configured to run under the Local Service, Network Service or Local System accounts. Local Service and Network Service services only require the **packagedServices** capability. Local System services require both the **packagedServices** and **localSystemServices** capabilities.<br/><br/>We don't recommend that you declare this capability in applications that you submit to the Microsoft Store. In most cases, the use of this capability won't be approved.  |
-| **Local System Services** | The **localSystemServices** restricted capability allows applications that are created by Microsoft partners and enterprises to install one or more Local System services along with the app (that is, your application can declare the StartAccount for the services to be LocalSystem). This scenario also requires the **packagesServices** capability. <br/><br/>We don't recommend that you declare this capability in applications that you submit to the Microsoft Store. In most cases, the use of this capability won't be approved. |
+| **Local System Services** | The **localSystemServices** restricted capability allows applications that are created by Microsoft partners and enterprises to install one or more Local System services along with the app (that is, your application can declare the StartAccount for the services to be LocalSystem). This scenario also requires the **packagedServices** capability. <br/><br/>We don't recommend that you declare this capability in applications that you submit to the Microsoft Store. In most cases, the use of this capability won't be approved. |
 | **Background Spatial Perception** | The **backgroundSpatialPerception** restricted capability allows an application to access the movement of the user's head, hands, motion controllers, and other tracked objects while the app is running in the background. |
 | **UI Access** | UIAccess is a feature in Windows that allows certain trusted applications to interact with the user interface (UI) of other applications, even when they are running with higher privileges or in a secure desktop session. This feature is often used by accessibility tools and automation software to provide users with alternative ways to interact with applications. The **uiAccess** restricted capability must be specified when the *uiAccess* attribute of the **requestedExecutionLevel** element is set to true in the app manifest file. For more information see, [Security Considerations for Assistive Technologies](/windows/win32/winauto/uiauto-securityoverview). |