Updated common issues article for current Microsoft style

Author: DougKlopfenstein

powerquery-docs/common-issues.md

@@ -14,25 +14,25 @@ ms.author: miescobar
 
 ### Preserving sort
 
-You might assume that if you sort your data, any downstream operations will preserve the sort order.
+You might assume that if you sort your data, any downstream operations preserve the sort order.
 
-For example, if you sort a sales table so that each store's largest sale is shown first, you might expect that doing a "Remove duplicates" operation will return only the top sale for each store. And this operation might, in fact, appear to work. However, this behavior isn't guaranteed.
+For example, if you sort a sales table so that each store's largest sale is shown first, you might expect that doing a "Remove duplicates" operation returns only the top sale for each store. And this operation might, in fact, appear to work. However, this behavior isn't guaranteed.
 
 Because of the way Power Query optimizes certain operations, including skipping them or offloading them to data sources (which can have their own unique ordering behavior), sort order isn't guaranteed to be preserved through aggregations (such as `Table.Group`), merges (such as `Table.NestedJoin`), or duplicate removal (such as `Table.Distinct`).
 
 There are a number of ways to work around this. Here are a few suggestions:
 
 * Perform a sort *after* applying the downstream operation. For example, when grouping rows, sort the nested table in each group before applying further steps. Here's some sample M code that demonstrates this approach: `Table.Group(Sales_SalesPerson, {"TerritoryID"}, {{"SortedRows", each Table.Sort(_, {"SalesYTD", Order.Descending})}})`
-* Buffer the data (using `Table.Buffer`) before applying the downstream operation. In some cases, this operation will cause the downstream operation to preserve the buffered sort order.
+* Buffer the data (using `Table.Buffer`) before applying the downstream operation. In some cases, this operation causes the downstream operation to preserve the buffered sort order.
 * Use [ranking](rank-column.md). For example, instead of using `Table.Distinct`, you could order by the column(s) containing the duplicate values, rank based on a tie-breaker column (such as `modified_date`), and then filter to keep just the rank 1 rows.
 
 ### Data type inference
 
-Sometimes Power Query may incorrectly detect a column's data type. This is due to the fact that Power Query infers data types using only the first 200 rows of data. If the data in the first 200 rows is somehow different than the data after row 200, Power Query can end up picking the wrong type. (Be aware that an incorrect type won't always produce errors. Sometimes the resulting values will simply be incorrect, making the issue harder to detect.)
+Sometimes Power Query might incorrectly detect a column's data type. This is due to the fact that Power Query infers data types using only the first 200 rows of data. If the data in the first 200 rows is somehow different than the data after row 200, Power Query can end up picking the wrong type. (Be aware that an incorrect type won't always produce errors. Sometimes the resulting values are simply incorrect, making the issue harder to detect.)
 
-For example, imagine a column that contains integers in the first 200 rows (such as all zeroes), but contains decimal numbers after row 200. In this case, Power Query will infer the data type of the column to be Whole Number (Int64.Type). This inference will result in the decimal portions of any non-integer numbers being truncated.
+For example, imagine a column that contains integers in the first 200 rows (such as all zeroes), but contains decimal numbers after row 200. In this case, Power Query infers the data type of the column to be Whole Number (Int64.Type). This inference results in the decimal portions of any non-integer numbers being truncated.
 
-Or imagine a column that contains textual date values in the first 200 rows, and other kinds of text values after row 200. In this case, Power Query will infer the data type of the column to be Date. This inference will result in the non-date text values being treated as type conversion errors.
+Or imagine a column that contains textual date values in the first 200 rows, and other kinds of text values after row 200. In this case, Power Query infers the data type of the column to be Date. This inference results in the non-date text values being treated as type conversion errors.
 
 Because type detection works on the first 200 rows, but Data Profiling can operate over the entire data set, you can consider using the Data Profiling functionality to get an early indication in the Query Editor about Errors (from type detection or any number of other reasons) beyond the top N rows.
 
@@ -70,35 +70,35 @@ Cipher suites are used to encrypt messages to secure a network connection betwee
 
 These are the cipher suites the server you connect to must support to connect from Power Query Online or Power BI.
 
-In Power Query Desktop (Power BI, Excel), we don’t control your cipher suites. If you're trying to connect to Power Platform  (for example Power Platform Dataflows) or the Power BI Service, you'll need one of those cipher suites enabled on your OS. You may either upgrade the [Windows version](/windows/win32/secauthn/cipher-suites-in-schannel) or update the [Windows TLS registry](/windows-server/security/tls/tls-registry-settings) to make sure that your server endpoint supports one of these ciphers.
+In Power Query Desktop (Power BI, Excel), we don’t control your cipher suites. If you're trying to connect to Power Platform  (for example Power Platform Dataflows) or the Power BI Service, you need one of those cipher suites enabled on your OS. You may either upgrade the [Windows version](/windows/win32/secauthn/cipher-suites-in-schannel) or update the [Windows TLS registry](/windows-server/security/tls/tls-registry-settings) to make sure that your server endpoint supports one of these ciphers.
 
 To verify that your server complies with the security protocol, you can perform a test using a TLS cipher and scanner tool. One example might be [SSLLABS](https://www.ssllabs.com/ssltest/analyze.html).
 
 Customers must upgrade their servers before March 1, 2021. For more information about configuring TLS Cipher Suite order, see [Manage Transport Layer Security (TLS)](/windows-server/security/tls/manage-tls).
 
 ### Certificate revocation
 
-An upcoming version of Power BI Desktop will cause SSL connections failure from Desktop when any certificates in the SSL chain are missing certificate revocation status. This  is a change from the current state, where revocation only caused connection failure in the case where the certificate was explicitly revoked. Other certificate issues might include invalid signatures, and certificate expiration.
+An upcoming version of Power BI Desktop causes SSL connections failure from Desktop when any certificates in the SSL chain are missing certificate revocation status. This  is a change from the current state, where revocation only caused connection failure in the case where the certificate was explicitly revoked. Other certificate issues might include invalid signatures, and certificate expiration.
 
-As there are configurations in which revocation status may be stripped, such as with corporate proxy servers, we'll be providing another option to ignore certificates that don't have revocation information. This option will allow situations where revocation information is stripped in certain cases, but you don't want to lower security entirely, to continue working.
+As there are configurations in which revocation status might be stripped, such as with corporate proxy servers, we'll be providing another option to ignore certificates that don't have revocation information. This option allows situations where revocation information is stripped in certain cases, but you don't want to lower security entirely, to continue working.
 
-It isn't recommended, but users will continue to be able to turn off revocation checks entirely.
+It isn't recommended, but users can continue to be able to turn off revocation checks entirely.
 
 ### Error: Evaluation was canceled
 
-Power Query will return the message "Evaluation was canceled" when background analysis is disabled and the user switches between queries or closes the Query Editor while a query is in the process of refreshing.
+Power Query returns the message "Evaluation was canceled" when background analysis is disabled and the user switches between queries or closes the Query Editor while a query is in the process of refreshing.
 
 ### Error: The key didn't match any rows in the table
 
-There are many reasons why Power Query may return an error that **the key didn't match any rows in the table**. When this error happens, the Mashup Engine is unable to find the table name it's searching for. Reasons why this error may happen include:
+There are many reasons why Power Query might return an error that **the key didn't match any rows in the table**. When this error happens, the Mashup Engine is unable to find the table name it's searching for. Reasons why this error might happen include:
 
 * The table name has been changed, for example in the data source itself.
 * The account used to access the table doesn't have sufficient privileges to read the table.
-* There may be multiple credentials for a single data source, which [isn't supported in Power BI Service when using Personal Cloud Connections](/power-bi/connect-data/refresh-data#accessing-cloud-data-sources). This error may happen, for example, when the data source is a cloud data source and multiple accounts are being used to access the data source at the same time with different credentials. If the data source is on-premises, you'll need to use the on-premises data gateway.
+* There can be multiple credentials for a single data source, which [isn't supported in Power BI Service when using Personal Cloud Connections](/power-bi/connect-data/refresh-data#accessing-cloud-data-sources). This error might happen, for example, when the data source is a cloud data source and multiple accounts are being used to access the data source at the same time with different credentials. If the data source is on-premises, you'll need to use the on-premises data gateway.
 
 ### Limitation: Domain-joined requirement for gateway machines when using Windows authentication
 
-Using Windows authentication with an on-premises gateway requires the gateway machine to be domain joined. This applies to any connections that are set up with “Windows authentication through the gateway”. Windows accounts that will be used to access a data source might require read access to the shared components in the Windows directory and the gateway installation.
+Using Windows authentication with an on-premises gateway requires the gateway machine to be domain joined. This applies to any connections that are set up with "Windows authentication through the gateway*. Windows accounts that are used to access a data source might require read access to the shared components in the Windows directory and the gateway installation.
 
 ### Limitation: Cross tenant OAuth2 refresh isn't supported in Power BI service