Update embed-azure-analysis-services.md

Author: mberdugo

powerbi-docs/developer/embedded/embed-azure-analysis-services.md

@@ -19,7 +19,7 @@ This article explains how to embed a Power BI report that uses data stored in [A
 
 ## Prerequisites
 
-You'll need a report with a live connection to AAS database, with or without RLS.
+You need a report with a live connection to AAS database, with or without RLS.
 
 ## Dynamic security - RLS
 
@@ -53,10 +53,10 @@ Use the [**service principal object ID**](embedded-troubleshoot.md#whats-the-dif
 
 ## Analysis Service migration
 
-You can [migrate from AAS to Power BI Premium](../../guidance/migrate-azure-analysis-services-to-powerbi-premium-migration-scenarios.md) even if you have an embedded AAS report. Your embedded report won't break during the migration, as long as the principal that's calling the [Embed Token - Generate Token](/rest/api/power-bi/embed-token/generate-token) API, is a member or admin of the workspace.
+You can [migrate from AAS to Power BI Premium](../../guidance/migrate-azure-analysis-services-to-powerbi-premium-migration-scenarios.md) even if you have an embedded AAS report. Your embedded report doesn't break during the migration, as long as the principal that's calling the [Embed Token - Generate Token](/rest/api/power-bi/embed-token/generate-token) API, is a member or admin of the workspace.
 
 >[!NOTE]
-> If the service principal is not an admin, and you don't want to make it an admin of the workspace when you migrate, migrate that model into a separate workspace where you can give it admin permissions.
+> If the service principal isn't an admin, and you don't want to make it an admin of the workspace when you migrate, migrate that model into a separate workspace where you can give it admin permissions.
 
 ## Generate an embed token
 
@@ -69,15 +69,15 @@ The information needed to generate an embed token depends on how you're connecte
 To generate an embed token, provide the following information:
 
 * **Username** (Optional if no RLS. Required for RLS) - The username must be the same as API caller (in this case, the Master user's [UPN](./pbi-glossary.md#user-principal-name-upn)). If the database doesn't use RLS, and no username is provided, the master user's credentials are used.
-* **Role** (required for RLS) - The report will only display data if the effective identity is a member of the role.
+* **Role** (required for RLS) - The report only displays data if the effective identity is a member of the role.
 
 Example:  
 
 Define the user identity and roles for one of the following three scenarios:
 
 * If RLS isn't implemented:
 
-There is no need to define any effective identity.
+You don't need to define any effective identity.
 
 * If using static RLS:
 
@@ -101,7 +101,7 @@ There is no need to define any effective identity.
   ```
 
     >[!NOTE]
-    >`customData` in the embed token cannot be larger than 1,024 characters.
+    >`customData` in the embed token can't be larger than 1,024 characters.
 
 Use the effective identity to generate an embed token:
 
@@ -176,7 +176,7 @@ public EmbedToken GetEmbedToken(Guid reportId, IList<Guid> datasetIds, [Optional
 
 ---
 
-Use the embed token to embed the report into your app or website. Your report will filter data according to the applied RLS in the report.
+Use the embed token to embed the report into your app or website. Your report filters data according to the applied RLS in the report.
 
 ## Related content