Live publish

Author: buck1ey

powerapps-docs/developer/data-platform/webapi/create-entity-web-api.md

@@ -73,7 +73,7 @@ To create a new entity record you must identify the valid property names and typ
 
 ## Create with data returned
 
-You can compose your `POST` request so that data from the created record will be returned with a status of `201 (Created)`.  To get his result, you must use the `return=representation` preference in the request headers.
+You can compose your `POST` request so that data from the created record will be returned with a status of `201 (Created)`.  To get this result, you must use the `return=representation` preference in the request headers.
 
 To control which properties are returned, append the `$select` query option to the URL to the entity set. You may also use `$expand` to return related entities.
 
@@ -347,4 +347,5 @@ More information: [Access documents faster using storage partitions](azure-stora
 [Impersonate another user using the Web API](impersonate-another-user-web-api.md)<br />
 [Perform conditional operations using the Web API](perform-conditional-operations-using-web-api.md)<br />
 
-[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
+

powerapps-docs/developer/data-platform/webapi/query-data-web-api.md

@@ -77,9 +77,9 @@ OData-Version: 4.0
 
 <a name="bkmk_limits"></a>
 
-## Limits on number of tables returned
+## Limits on number of rows (records) returned
 
- Unless you specify a smaller page size, a maximum of 5000 entities will be returned for each request. If there are more entities that match the query filter criteria, a `@odata.nextLink` property will be returned with the results. Use the value of the `@odata.nextLink` property with a new `GET` request to return the next page of entity data.  
+ Unless you specify a smaller page size, a maximum of 5000 rows will be returned for each request. If there are more rows that match the query filter criteria, a `@odata.nextLink` property will be returned with the results. Use the value of the `@odata.nextLink` property with a new `GET` request to return the next page of rows.  
 
 > [!NOTE]
 >  Queries on entity (table) definitions aren’t limited or paged. More information:[Query table definitions using the Web API](query-metadata-web-api.md)  
@@ -88,7 +88,7 @@ OData-Version: 4.0
 
 ### Use `$top` query option
 
-You can limit the number of results returned by using the `$top` system query option. The following example will return just the first three account entities.  
+You can limit the number of results returned by using the `$top` system query option. The following example will return just the first three account rows.  
 
 ```http 
 GET [Organization URI]/api/data/v9.1/accounts?$select=name,revenue&$top=3  
@@ -317,9 +317,9 @@ OData-MaxVersion: 4.0
 OData-Version: 4.0
 ```
 
-### Filter parent records based on values of child records
+### Filter parent rows (records) based on values of child records
 
-The example given below shows how you can use the [/any operator](#bkmk_anyoperator) to retrieve all the account records which have:
+The example given below shows how you can use the [/any operator](#bkmk_anyoperator) to retrieve all the account records that have:
 
 - any of their linked opportunity records' budget greater than or equal to 300, and
 - the opportunity records' have no description, or
@@ -341,7 +341,7 @@ OData-Version: 4.0
 
 <a name="BKMK_FilterNavProperties"></a>
 
-### Filter records based on single-valued navigation property
+### Filter rows (records) based on single-valued navigation property
 
 Navigation properties let you access data related to the current entity. *Single-valued* navigation properties correspond to Lookup attributes that support many-to-one relationships and allow setting a reference to another entity. More information: [Navigation properties](web-api-types-operations.md#bkmk_navprops).  
 
@@ -787,9 +787,9 @@ OData-Version: 4.0
 
 <a bkmk="bkmk_retrieverelatedentitysingleandcollectionnavprop"></a>
 
-### Retrieve related tables by expanding both single-valued and collection-valued navigation properties
+### Retrieve related rows (records) by expanding both single-valued and collection-valued navigation properties
 
-The following example demonstrates how you can expand related entities for entity sets using both single and collection-valued navigation properties. As explained earlier, expanding on collection-valued navigation properties to retrieve related entities for entity sets returns an `@odata.nextLink` property for the related entities. You should use the value of the `@odata.nextLink` property with a new `GET` request to return the required data.  
+The following example demonstrates how you can expand related rows (records) for entity sets using both single and collection-valued navigation properties. As explained earlier, expanding on collection-valued navigation properties to retrieve related entities for entity sets returns an `@odata.nextLink` property for the related entities. You should use the value of the `@odata.nextLink` property with a new `GET` request to return the required data.  
 
 In this example, we are retrieving the contact and tasks assigned to the top 3 accounts.  
 

powerapps-docs/maker/TOC.yml

@@ -2182,8 +2182,12 @@
           href: ../teams/issue-reporting.md
         - name: Milestones
           href: ../teams/milestones.md
-        - name: Perspectives (Preview)
-          href: ../teams/perspectives.md
+        - name: Perspectives
+          items:
+            - name: Perspectives (Preview)
+              href: ../teams/perspectives.md
+            - name: Understand Perspectives (Preview) sample app architecture
+              href: ../teams/perspectives-architecture.md
         - name: Profile+ (Preview)
           href: ../teams/profile-app.md
         - name: Customize sample apps