Update how-to-tsi-gen2-migration.md

Author: tedvilutis

articles/time-series-insights/how-to-tsi-gen2-migration.md

@@ -51,9 +51,9 @@ Data
     1.	From Event Hubs (or IoT Hub) metrics, retrieve the rate of how much data it's ingested per day. From the Storage Account connected to the TSI environment, retrieve how much data there is in the blob container used by TSI. This information will be used to compute the ideal size of an ADX Cluster for your environment. 
     1.	Open [the Azure Data Explorer Cost Estimator](https://dataexplorer.azure.com/AzureDataExplorerCostEstimator.html) and fill the existing fields with the information found. Set “Workload type” as “Storage Optimized”, and "Hot Data" with the total amount of data queried actively.
     1.	After providing all the information, Azure Data Explorer Cost Estimator will suggest a VM size and number of instances for your cluster. Analyze if the size of actively queried data will fit in the Hot Cache. Multiply the number of instances suggested by the cache size of the VM size, per example: 
-        | Cost Estimator suggestion | Total Hot Cache suggested |
-        | ---| ---|
-        | 9x DS14 + 4 TB (cache) | 36 TB = [9x (instances) x 4 TB (of Hot Cache per node)] |
+| Cost Estimator suggestion | Total Hot Cache suggested |
+| ---| ---|
+| 9x DS14 + 4 TB (cache) | 36 TB = [9x (instances) x 4 TB (of Hot Cache per node)] |
 
     1. More factors to consider:
         - Environment growth: when planning the ADX Cluster size consider the data growth along the time.