Merge pull request #6761 from srThibaultP/patch-3

Fix typos and tables

Author: ktoliver

docs/dmx/select-distinct-from-model-dmx.md

@@ -18,7 +18,6 @@ author: minewiskan
 ## Syntax  
 
 ```  
-  
 SELECT [FLATTENED] DISTINCT [TOP <n>] <expression list> FROM <model>   
 [WHERE <condition list>][ORDER BY <expression>]  
 ```  
@@ -68,7 +67,6 @@ FROM [TM Decision Tree]
 
 |Gender|  
 |------------|  
-||  
 |F|  
 |M|  
 
@@ -88,16 +86,15 @@ FROM [TM Decision Tree]
 
 |Midpoint Age|Minimum Age|Maximum Age|  
 |------------------|-----------------|-----------------|  
-||||  
 |62|26|97|  
 
  The query also returns a single row of null values, to represent missing values.  
 
 ## Discretized Column Example  
- The following code sample returns the midpoint, maximum, and minimum values for each bucket that has been created by the algorithm for the column, [`Yearly Income]`. To reproduce the results for this example, you must create a new mining structure that is the same as `[Targeted Mailing]`. In the wizard, change the content type of the `Yearly Income` column from **Continuous** to **Discretized**.  
+ The following code sample returns the midpoint, maximum, and minimum values for each bucket that has been created by the algorithm for the column, `[Yearly Income]`. To reproduce the results for this example, you must create a new mining structure that is the same as `[Targeted Mailing]`. In the wizard, change the content type of the `Yearly Income` column from **Continuous** to **Discretized**.  
 
 > [!NOTE]  
->  You can also change the mining model created in the Basic Mining Tutorial to discretize the mining structure column, [`Yearly Income]`. For information about how to do this, see [Change the Discretization of a Column in a Mining Model](/analysis-services/data-mining/change-the-discretization-of-a-column-in-a-mining-model). However, when you change the discretization of the column, it will force the mining structure to be reprocessed, which will change the results of other models that you have built using that structure.  
+>  You can also change the mining model created in the Basic Mining Tutorial to discretize the mining structure column, `[Yearly Income]`. For information about how to do this, see [Change the Discretization of a Column in a Mining Model](/analysis-services/data-mining/change-the-discretization-of-a-column-in-a-mining-model). However, when you change the discretization of the column, it will force the mining structure to be reprocessed, which will change the results of other models that you have built using that structure.  
   
 ```  
 SELECT DISTINCT [Yearly Income] AS [Bucket Average],   
@@ -110,14 +107,13 @@ FROM [TM Decision Tree]
 
 |Bucket Average|Bucket Minimum|Bucket Maximum|  
 |--------------------|--------------------|--------------------|  
-||||  
 |24610.7|10000|39221.41|  
 |55115.73|39221.41|71010.05|  
 |84821.54|71010.05|98633.04|  
 |111633.9|98633.04|124634.7|  
 |147317.4|124634.7|170000|  
 
- You can see that the values of the [Yearly Income] column have been discretized into five buckets, plus an additional row of null values, to represent missing values.  
+ You can see that the values of the `[Yearly Income]` column have been discretized into five buckets, plus an additional row of null values, to represent missing values.  
 
  The number of decimal places in the results depends on the client that you use for querying. Here they have been rounded to two decimal places, both for simplicity and to reflect the values that are displayed in [!INCLUDE[ssBIDevStudioFull](../includes/ssbidevstudiofull-md.md)].