Updating image format

Author: JasonWHowell

articles/hdinsight/find-host-name.md

@@ -23,7 +23,7 @@ You can get the host names through Ambari UI or Ambari REST API.
 ## Get the host names from Ambari Web UI
 You can use Ambari Web UI to get the host names when you SSH to the node. The Ambari Web UI hosts view is available on your HDInsight cluster at `https://CLUSTERNAME.azurehdinsight.net/#/main/hosts`, where `CLUSTERNAME` is the name of your cluster.
 
-![Get-Host-Names-In-Ambari-UI](.\media\find-host-name\find-host-name-in-ambari-ui.png)
+:::image type="content" border="true" source=".\media\find-host-name\find-host-name-in-ambari-ui.png" alt-text="Get-Host-Names-In-Ambari-UI":::
 
 ## Get the host names from Ambari REST API
 When building automation scripts,  you can use the Ambari REST API to get the host names before you make connections to hosts. The numbers in the host name are not guaranteed in sequence and HDInsight may change the host name format to align with VMs with release refresh. Don’t take the dependency on any certain naming convention that exists today. 

articles/hdinsight/hbase/quickstart-resource-manager-template.md

@@ -67,7 +67,7 @@ After you complete the quickstart, you may want to delete the cluster. With HDIn
 
 From the Azure portal, navigate to your cluster, and select **Delete**.
 
-![Delete Resource Manager template HBase](./media/quickstart-resource-manager-template/azure-portal-delete-hbase.png)
+:::image type="content" border="true" source="./media/quickstart-resource-manager-template/azure-portal-delete-hbase.png" alt-text="Delete Resource Manager template HBase":::
 
 You can also select the resource group name to open the resource group page, and then select **Delete resource group**. By deleting the resource group, you delete both the HDInsight cluster, and the default storage account.
 

articles/hdinsight/hbase/troubleshoot-data-retention-issues-expired-data.md

@@ -34,7 +34,7 @@ Follow the steps given to understand where is the issue. Start by checking if th
    describe 'table_name'
    ```
 
-   ![Screenshot showing describe table name command.](media/troubleshoot-data-retention-issues-expired-data/image-1.png)
+   :::image type="content" border="true" source="media/troubleshoot-data-retention-issues-expired-data/image-1.png" alt-text="Screenshot showing describe table name command.":::
 
 1. If not configured, default TTL is set to 'FOREVER.' There are two possibilities why data is not expired as expected and removed from query result.
 
@@ -55,7 +55,7 @@ Follow the steps given to understand where is the issue. Start by checking if th
    hdfs dfs -ls -R /hbase/data/default/table_name/ | grep "column_family_name"
    ```
 
-   ![Screenshot showing check size of store file command.](media/troubleshoot-data-retention-issues-expired-data/image-2.png)
+   :::image type="content" border="true" source="media/troubleshoot-data-retention-issues-expired-data/image-2.png" alt-text="Screenshot showing check size of store file command.":::
 
 1. Likely, there are more results shown in the output, one result for each region ID that is part of the table and between 0 and more results for StoreFiles present under each region name, for the selected ColumnFamily. To count the overall number of rows in the result output above, run the following command.
 
@@ -79,7 +79,7 @@ Follow the steps given to understand where is the issue. Start by checking if th
 
 1. An additional store file is created compared to previous result output for each region where data is modified, the StoreFile includes current content of MemStore for that region.
 
-   ![Screenshot showing memory store for the region.](media/troubleshoot-data-retention-issues-expired-data/image-3.png)
+   :::image type="content" border="true" source="media/troubleshoot-data-retention-issues-expired-data/image-3.png" alt-text="Screenshot showing memory store for the region.":::
 
 ### Check the number and size of StoreFiles per table per region after major compaction
 
@@ -107,11 +107,11 @@ Follow the steps given to understand where is the issue. Start by checking if th
 
 1. You will notice that an extra StoreFile has been created in addition to previous ones per region per ColumnFamily and after several moments only the last created StoreFile is kept per region per column family.
 
-   ![Screenshot showing store file as column family.](media/troubleshoot-data-retention-issues-expired-data/image-4.png)
+   :::image type="content" border="true" source="media/troubleshoot-data-retention-issues-expired-data/image-4.png" alt-text="Screenshot showing store file as column family.":::
 
 For the example region above, once the extra moments elapse, we can notice that one single StoreFile remained and the size occupied by this file on the storage is reduced as major compaction occurred and at this point any expired data that has not been deleted before(by another major compaction), will be deleted after running current major compaction operation.
 
-![Screenshot showing expired data not deleted.](media/troubleshoot-data-retention-issues-expired-data/image-5.png)
+:::image type="content" border="true" source="media/troubleshoot-data-retention-issues-expired-data/image-5.png" alt-text="Screenshot showing expired data not deleted.":::
 
 > [!NOTE]
 > For this troubleshooting exercise we triggered the major compaction manually. But in practice, doing that manually for many tables might be time consuming. By default, major compaction is disabled on HDInsight cluster. The main reason for keeping major compaction disabled by default is because the performance of the table operations is impacted when a major compaction is in progress. However, you can enable major compaction by configuring the value for the property hbase.hregion.majorcompaction in ms or can use a cron tab job or another external system to schedule compaction at a time convenient for you, with lower workload.

articles/hdinsight/hdinsight-config-for-vscode.md

@@ -20,7 +20,7 @@ For general information about working with settings in VS Code, refer to [User a
 3. Search **Set Configuration**.
 4. Expand **Extensions** in the left directory, and select **HDInsight configuration**.
 
- ![hdi config image](./media/HDInsight-config-for-vscode/HDInsight-config-for-vscode.png)
+ :::image type="content" border="true" source="./media/HDInsight-config-for-vscode/HDInsight-config-for-vscode.png" alt-text="hdi config image":::
 
 ## General settings   
 

articles/hdinsight/hdinsight-for-vscode.md

@@ -496,7 +496,7 @@ From the menu bar, go to **View** > **Command Palette**, and then enter **Azure:
 
  For Synapse PySpark installation error, since its dependency will not be maintained anymore by other team, it will not be maintained anymore. If you trying to use Synapse Pyspark interactive, please use [Azure Synapse Analytics](https://ms.web.azuresynapse.net/) instead. And it's a long term change.
 
-   ![synapse pyspark installation error](./media/hdinsight-for-vscode/known-issue.png)
+   :::image type="content" border="true" source="./media/hdinsight-for-vscode/known-issue.png" alt-text="synapse pyspark installation error":::
 
 
 ## Next steps