Changed App Catalog to app catalog

Per style guidelines

Author: Linda Caputo

docs/apis/alm-api-for-spfx-add-ins.md

@@ -10,11 +10,11 @@ ms.assetid: fdf7ecb2-8851-425b-b058-3285fba77b68
 
 ALM APIs provide simple APIs to manage deployment of your SharePoint Framework solutions and add-ins across your tenant. ALM APIs support the following capabilities:
 
-- Add SharePoint Framework solution or SharePoint Add-in to tenant App Catalog.
-- Enable SharePoint Framework solution or SharePoint Add-in to be available for installation in tenant App Catalog.
-- Disable SharePoint Framework solution or SharePoint Add-in not to be available for installation in tenant App Catalog.
-- Install SharePoint Framework solution or SharePoint Add-in from tenant App Catalog to a site.
-- Upgrade SharePoint Framework solution or SharePoint Add-in to a site, which has a newer version available in the tenant App Catalog.
+- Add SharePoint Framework solution or SharePoint Add-in to tenant app catalog.
+- Enable SharePoint Framework solution or SharePoint Add-in to be available for installation in tenant app catalog.
+- Disable SharePoint Framework solution or SharePoint Add-in not to be available for installation in tenant app catalog.
+- Install SharePoint Framework solution or SharePoint Add-in from tenant app catalog to a site.
+- Upgrade SharePoint Framework solution or SharePoint Add-in to a site, which has a newer version available in the tenant app catalog.
 - Uninstall SharePoint Framework solution or SharePoint Add-in from the site.
 
 ALM APIs can be used to perform exactly the same operations that are available from a UI perspective. When these APIs are used, all typical actions are performed. Following are some of the characteristics of ALM APIs:
@@ -25,13 +25,13 @@ ALM APIs can be used to perform exactly the same operations that are available f
 ALM APIs are natively provided by using REST APIs, but there are also additional CSOM extensions and PowerShell cmdlets available through SharePoint Patterns and Practices.
 
 > [!NOTE] 
-> ALM APIs are not currently supported for the [site collection App Catalog](../general-development/site-collection-app-catalog.md). Support will be added in early 2018.
+> ALM APIs are not currently supported for the [site collection app catalog](../general-development/site-collection-app-catalog.md). Support will be added in early 2018.
 
 ## REST API
 
-### Add solution packages to the tenant App Catalog 
+### Add solution packages to the tenant app catalog 
 
-This API is designed to be executed in the context of the tenant App Catalog site.
+This API is designed to be executed in the context of the tenant app catalog site.
 
 ```
 url: /_api/web/tenantappcatalog/Add(overwrite=true, url='test.txt')
@@ -40,9 +40,9 @@ binaryStringRequestBody: true
 body: 'byte array of the file'
 ```
 
-### Deploy solution packages in the tenant App Catalog
+### Deploy solution packages in the tenant app catalog
 
-This enables the solution to be available to install to specific sites. This API is designed to be executed in the context of the tenant App Catalog site.
+This enables the solution to be available to install to specific sites. This API is designed to be executed in the context of the tenant app catalog site.
 
 ```
 url: /_api/web/tenantappcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')/Deploy
@@ -51,9 +51,9 @@ url: /_api/web/tenantappcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-x
 > [!NOTE]
 > This operation is required to be completed after Add before you can install packages to specific sites. 
 
-### Retract solution packages in the tenant App Catalog
+### Retract solution packages in the tenant app catalog
 
-This retracts the solution to be available from the sites. This API is designed to be executed in the context of the tenant App Catalog site.
+This retracts the solution to be available from the sites. This API is designed to be executed in the context of the tenant app catalog site.
 
 ```
 url: /_api/web/tenantappcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')/Retract
@@ -62,9 +62,9 @@ url: /_api/web/tenantappcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-x
 > [!NOTE]
 > If you run this operation after you have installed solutions to the site, they will stop working because the solution is disabled from the tenant level.
 
-### Remove solution packages from the tenant App Catalog
+### Remove solution packages from the tenant app catalog
 
-This API is designed to be executed in the context of the tenant App Catalog site.
+This API is designed to be executed in the context of the tenant app catalog site.
 
 ```
 url: /_api/web/tenantappcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')/Remove
@@ -73,27 +73,27 @@ url: /_api/web/tenantappcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-x
 > [!NOTE]
 > If the Retract operation is not performed before the Remove operation, the solution is automatically retracted.
 
-### List available packages from the tenant App Catalog
+### List available packages from the tenant app catalog
 
-Use this REST API for getting a list of available SharePoint Framework solutions or add-ins in the tenant App Catalog.
+Use this REST API for getting a list of available SharePoint Framework solutions or add-ins in the tenant app catalog.
 
 ```
 url: /_api/web/tenantappcatalog/AvailableApps
 method: GET
 ```
 
-### Details about individual solution packages in the tenant App Catalog
+### Details about individual solution packages in the tenant app catalog
 
-Use this REST API for getting details about individual SharePoint Framework solutions or add-ins available in the tenant App Catalog.
+Use this REST API for getting details about individual SharePoint Framework solutions or add-ins available in the tenant app catalog.
 
 ```
 url: /_api/web/tenantappcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')
 method: GET
 ```
 
-### Install solution package from the tenant App Catalog to a SharePoint site
+### Install solution package from the tenant app catalog to a SharePoint site
 
-Install a solution package with a specific identifier from the tenant App Catalog to the site based on URL context. This REST call can be executed in the context of the site where the install operation should happen.
+Install a solution package with a specific identifier from the tenant app catalog to the site based on URL context. This REST call can be executed in the context of the site where the install operation should happen.
 
 ```
 url: /_api/web/tenantappcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')/Install
@@ -102,7 +102,7 @@ method: POST
 
 ### Upgrade solution packages on the SharePoint site
 
-Upgrade a solution package from the site to a newer version available in the tenant App Catalog. This REST call can be executed in the context of the site where the upgrade operation should happen.
+Upgrade a solution package from the site to a newer version available in the tenant app catalog. This REST call can be executed in the context of the site where the upgrade operation should happen.
 
 ```
 url: /_api/web/tenantappcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')/Upgrade
@@ -125,9 +125,9 @@ method: POST
 
 By using [PnP PowerShell](https://docs.microsoft.com/en-us/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets?view=sharepoint-ps), you can automate deploying, publishing, installing, upgrading, and retracting your apps. 
 
-### Add and publish your app to the App Catalog
+### Add and publish your app to the app catalog
 
-Adding your app (.sppkg file, .app file) to the tenant App Catalog is a prerequisite to making your app available for use on your SharePoint sites. You can do so by using the following cmdlet:
+Adding your app (.sppkg file, .app file) to the tenant app catalog is a prerequisite to making your app available for use on your SharePoint sites. You can do so by using the following cmdlet:
 
 ```PowerShell
 Add-PnPApp -Path ./myapp.sppkg
@@ -145,7 +145,7 @@ Publish-PnPApp -Identity <app id> -SkipFeatureDeployment
 
 
 
-### Remove the app from the App Catalog
+### Remove the app from the app catalog
 
 To remove an app added earlier, use the following cmdlet:
 
@@ -156,7 +156,7 @@ Remove-PnPApp -Identity <app id>
 
 ### Use apps on your site
 
-After the app is added to the App Catalog and published, you can install the app to your site:
+After the app is added to the app catalog and published, you can install the app to your site:
 
 ```PowerShell
 Install-PnPApp -Identity <app id>

docs/general-development/create-a-workflow-with-elevated-permissions-by-using-the-sharepoint-workflo.md

@@ -118,7 +118,7 @@ Finally, you need to wrap the workflow actions inside an App Step. The following
 
 ### To wrap actions inside an App Step
 
-1. Open the App Catalog site in SharePoint Designer.    
+1. Open the app catalog site in SharePoint Designer.    
 
 2. Create a new Custom List on which to run the workflow. In this example, the list name is **App Demo**.    
 

docs/general-development/site-collection-app-catalog.md

@@ -112,4 +112,4 @@ Before deploying solutions to site collection app catalogs, site collection admi
 
 ## See also
 
-- [Manage the Site Collection App Catalog](https://support.office.com/en-us/article/Manage-the-Site-Collection-App-Catalog-928b9b61-a9de-4563-a7d1-6231aa9d4d19)
+- [Manage the Site Collection app catalog](https://support.office.com/en-us/article/Manage-the-Site-Collection-App-Catalog-928b9b61-a9de-4563-a7d1-6231aa9d4d19)

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

@@ -76,7 +76,7 @@ Conceptually, the hierarchy of SharePoint objects is expressed in terms of conta
 ## add-ins for SharePoint
 <a name="sectionSection3"> </a>
 
-add-ins for SharePoint are lightweight solutions that don't install on the SharePoint host server, which means they don't make excessive API calls to the host server. You can build add-ins for SharePoint by using the Cloud Add-in Model. Users can discover and download add-ins from the Office Store or from the enterprise's App Catalog. For more information, see  [Overview of add-ins for SharePoint](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70.aspx). 
+add-ins for SharePoint are lightweight solutions that don't install on the SharePoint host server, which means they don't make excessive API calls to the host server. You can build add-ins for SharePoint by using the Cloud Add-in Model. Users can discover and download add-ins from the Office Store or from the enterprise's app catalog. For more information, see  [Overview of add-ins for SharePoint](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70.aspx). 
 
 ## File system and content databases, and how they work together
 <a name="sectionSection4"> </a>

docs/solution-guidance/development-experience-tenant-apponly-permissions-in-sharepoint-online.md

@@ -45,7 +45,7 @@ Supply the **Client ID** and **Client Secret **created in Step 1.
 Since you want to debug the add-in, ensure that you supply https://localhost.com including the port as depicted below.
 ![](http://i.imgur.com/nQmSbPC.png)
 
-Now deploy the add-in in the App Catalog site.
+Now deploy the add-in in the app catalog site.
 
 ### Step 5: Install your add-in in your developer site collection
 
@@ -55,7 +55,7 @@ Navigate to the developer site and add the app. Click on **App Details**.
 If you clicked on the app tile, you will have to click on "**Find out why**" and request your app
 ![](http://i.imgur.com/DwWUkG0.png)
 
-Once the request has been submitted the status will be in a pending state until the SharePoint Administrator or the App Catalog Administrator approves the request. To approve the request, navigate to the app catalog, App Requests and approve the request.
+Once the request has been submitted the status will be in a pending state until the SharePoint Administrator or the app catalog Administrator approves the request. To approve the request, navigate to the app catalog, App Requests and approve the request.
 
 ![](http://i.imgur.com/yZ8vNEc.png)
 

docs/solution-guidance/feature-stapling-sharepoint-add-in.md

@@ -50,12 +50,12 @@ The following article describes how to staple features to a site definition.
 
 Staple Add-ins
 --------------
-In this pattern you deploy Add-ins stored in the App Catalog to specific site collections, managed paths, and site templates.
+In this pattern you deploy Add-ins stored in the app catalog to specific site collections, managed paths, and site templates.
 
 - See the [SharePoint 2013 App Deployment through 'App Stapling' (MSDN Blog Article - Richard DiZerega)](http://blogs.msdn.com/b/richard_dizeregas_blog/archive/2013/09/18/10399333.aspx) for more details about the Add-in stapling model.
 - Because the add-in is pushed by an administrator, site owners will not be able to remove the add-in from a site that meets the deployment criteria.  Not even a site collection administrator can remove the add-in.
-- This centralized deployment also shares the same centralized add-in resources (Add-in Web and Remote Web).  Essentially, the Add-in is deployed, but not installed in the sites.  All sites will leverage the Add-in Web and Remote Web from the instance installed in the App Catalog.
-- Because of centralized deployment, remote events such as 'Handle App Installed', 'Handle App Uninstalled', and 'Handle App Upgrade' will only fire once (when the Add-In is installed in the App Catalog).
+- This centralized deployment also shares the same centralized add-in resources (Add-in Web and Remote Web).  Essentially, the Add-in is deployed, but not installed in the sites.  All sites will leverage the Add-in Web and Remote Web from the instance installed in the app catalog.
+- Because of centralized deployment, remote events such as 'Handle App Installed', 'Handle App Uninstalled', and 'Handle App Upgrade' will only fire once (when the Add-In is installed in the app catalog).
 	+ This can make it difficult to use the Add-in stapling pattern to automatically apply changes to sites where it is deployed because these events do not fire when it is deployed to sites.
 - Add-in parts are not supported when Add-ins are stapled to sites.
 - This pattern requires manual user actions to deploy the Add-ins.

docs/sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-___domain-library.md

@@ -361,7 +361,7 @@ To switch the context site in your code, use the **AppContextSite** endpoint (RE
 
 Here is a reminder of the REST endpoint: /_api/SP.AppContextSite(@target)/web/title?@target='weburl', and an example on how to instantiate the object in JSOM: `appContextSite = new SP.AppContextSite(context, weburl);`.
 
-As a developer, you can only deploy tenant-scoped add-ins from the add-in catalog. You can provision an add-in catalog to your on-premises or SharePoint Online environments. Uploading your add-in to the add-in catalog is as simple as uploading a file to a document library. For detailed instructions, see [Use the App Catalog to make custom business apps available for your SharePoint Online environment](https://support.office.com/en-us/article/Use-the-App-Catalog-to-make-custom-business-apps-available-for-your-SharePoint-Online-environment-0b6ab336-8b83-423f-a06b-bcc52861cba0?CorrelationId=94979966-ff7b-4e00-985a-5c9e614b35c9&ui=en-US&rs=en-US&ad=US&ocmsassetID=HA102772362).
+As a developer, you can only deploy tenant-scoped add-ins from the add-in catalog. You can provision an add-in catalog to your on-premises or SharePoint Online environments. Uploading your add-in to the add-in catalog is as simple as uploading a file to a document library. For detailed instructions, see [Use the app catalog to make custom business apps available for your SharePoint Online environment](https://support.office.com/en-us/article/Use-the-App-Catalog-to-make-custom-business-apps-available-for-your-SharePoint-Online-environment-0b6ab336-8b83-423f-a06b-bcc52861cba0?CorrelationId=94979966-ff7b-4e00-985a-5c9e614b35c9&ui=en-US&rs=en-US&ad=US&ocmsassetID=HA102772362).
 
 From the add-in catalog, you can deploy the add-in to one or more websites in the tenant. Because your add-in has permissions to access data in the tenant, you only have to deploy to one website to access data on the whole tenant. For instructions on how to deploy an add-in from the add-in catalog, see [Deploy a custom add-in](https://support.office.com/en-us/article/Use-the-App-Catalog-to-make-custom-business-apps-available-for-your-SharePoint-Online-environment-0b6ab336-8b83-423f-a06b-bcc52861cba0?CorrelationId=94979966-ff7b-4e00-985a-5c9e614b35c9&ui=en-US&rs=en-US&ad=US&ocmsassetID=HA102772362) 
 

docs/spfx/call-microsoft-graph-using-graphhttpclient.md

@@ -179,8 +179,8 @@ The code needs to call the **GraphHttpClient** application that runs on SharePoi
   ```
 
 2. Deploy the solution to your SharePoint tenant:
-  * Go to your site's App Catalog.
-  * Upload or drag and drop the **hellograph-webpart.sppkg** to the App Catalog.
+  * Go to your site's app catalog.
+  * Upload or drag and drop the **hellograph-webpart.sppkg** to the app catalog.
   * When prompted, if you trust the **hellograph-webpart-client-side-solution**, select **Make this solution available to all sites in the organization**, and select **Deploy**.
 
 3. Use gulp serve to host the web part.
@@ -282,8 +282,8 @@ Again, you need to modify the HTML to add a button that creates a new group.
   ```
 
 2. Deploy the solution to your SharePoint tenant:
-  * Go to your site's App Catalog.
-  * Upload or drag and drop the **hellograph-webpart.sppkg** to the App Catalog.
+  * Go to your site's app catalog.
+  * Upload or drag and drop the **hellograph-webpart.sppkg** to the app catalog.
   * Because your solution is already registered, you are prompted as to whether you want to replace it. Select **Replace it**.
   * When prompted as to whether you trust the solution, select **Deploy**.