Skip to content

Commit 507f4a1

Browse files
committed
clarify confusing grammer
- fixes 6813
1 parent 5a5e119 commit 507f4a1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/sp-add-ins/context-token-oauth-flow-for-sharepoint-add-ins.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Context Token OAuth flow for SharePoint Add-ins
33
description: The OAuth authentication and authorization flow for low-trust, provider-hosted add-ins in SharePoint.
4-
ms.date: 05/01/2020
4+
ms.date: 03/23/2021
55
ms.prod: sharepoint
66
localization_priority: Priority
77
---
@@ -28,7 +28,7 @@ There are three tokens involved: SharePoint has ACS create a **context token** t
2828

2929
The following preliminary steps must be completed before a SharePoint Add-in can use the Context Token flow:
3030

31-
- If the SharePoint Add-in is to be installed to an on-premises SharePoint farm, these setup requirements don't apply if it is only installed to SharePoint Online:
31+
- The following requirements only apply if you're installing the SharePoint Add-in on-premises in addition to SharePoint Online; these requirements don't apply if you're only installing the SharePoint Add-in to SharePoint Online
3232

3333
- **The farm must be configured to support add-ins**. This is actually a requirement for installing any SharePoint Add-ins to the farm, even if they don't use the Context Token flow. For more information, see [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins.md).
3434
- **The customer who is installing the add-in must have an Office 365 account**. This is necessary to get access to ACS. The customer does not have to use their account for any other purpose.

0 commit comments

Comments
 (0)