Merge pull request #88115 from dagiro/cats50

cats50

Author: v-shils

articles/hdinsight/domain-joined/apache-domain-joined-manage.md

@@ -4,7 +4,7 @@ description: Learn how to manage Azure HDInsight clusters with Enterprise Securi
 ms.service: hdinsight
 author: omidm1
 ms.author: omidm
-ms.reviewer: mamccrea
+ms.reviewer: jasonh 
 ms.custom: hdinsightactive
 ms.topic: conceptual
 ms.date: 08/24/2018

articles/hdinsight/domain-joined/apache-domain-joined-run-hive.md

@@ -4,11 +4,12 @@ description: Learn how to configure Apache Ranger policies for Hive in an Azure
 ms.service: hdinsight
 author: omidm1
 ms.author: omidm
-ms.reviewer: mamccrea
+ms.reviewer: jasonh
 ms.custom: hdinsightactive
 ms.topic: conceptual
 ms.date: 09/24/2018
 ---
+
 # Configure Apache Hive policies in HDInsight with Enterprise Security Package
 Learn how to configure Apache Ranger policies for Apache Hive. In this article, you create two Ranger policies to restrict access to the hivesampletable. The hivesampletable comes with HDInsight clusters. After you have configured the policies, you use Excel and ODBC driver to connect to Hive tables in HDInsight.
 

articles/hdinsight/domain-joined/hdinsight-use-oozie-domain-joined-clusters.md

@@ -4,11 +4,12 @@ description: Secure Apache Oozie workflows using the Azure HDInsight Enterprise
 ms.service: hdinsight
 author: omidm1
 ms.author: omidm
-ms.reviewer: mamccrea
+ms.reviewer: jasonh
 ms.custom: hdinsightactive,seodec18
 ms.topic: conceptual
 ms.date: 02/15/2019
 ---
+
 # Run Apache Oozie in HDInsight Hadoop clusters with Enterprise Security Package
 
 Apache Oozie is a workflow and coordination system that manages Apache Hadoop jobs. Oozie is integrated with the Hadoop stack, and it supports the following jobs:

articles/hdinsight/hdinsight-hadoop-create-linux-clusters-dotnet-sdk.md

@@ -1,14 +1,15 @@
 ---
 title: Create Apache Hadoop clusters using .NET - Azure HDInsight 
 description: Learn how to create Apache Hadoop, Apache HBase, Apache Storm, or Apache Spark clusters on Linux for HDInsight using the HDInsight .NET SDK.
-author: mamccrea
+author: hrasheed-msft
 ms.reviewer: jasonh
 ms.service: hdinsight
 ms.custom: hdinsightactive
 ms.topic: conceptual
 ms.date: 08/16/2018
-ms.author: mamccrea
+ms.author: hrasheed
 ---
+
 # Create Linux-based clusters in HDInsight using the .NET SDK
 
 [!INCLUDE [selector](../../includes/hdinsight-create-linux-cluster-selector.md)]

articles/hdinsight/storm/apache-storm-develop-csharp-visual-studio-topology.md

@@ -9,6 +9,7 @@ ms.topic: conceptual
 ms.date: 11/27/2017
 ROBOTS: NOINDEX
 ---
+
 # Develop C# topologies for Apache Storm by using the Data Lake tools for Visual Studio
 
 Learn how to create a C# Apache Storm topology by using the Azure Data Lake (Apache Hadoop) tools for Visual Studio. This document walks through the process of creating a Storm project in Visual Studio, testing it locally, and deploying it to an Apache Storm on Azure HDInsight cluster.
@@ -149,7 +150,7 @@ For an example topology that uses this component and works with Storm on HDInsig
 
    * **NextTuple**: Called by Storm when the spout is allowed to emit new tuples.
 
-   * **Ack** (transactional topology only): Handles acknowledgements initiated by other components in the topology for tuples sent from the spout. Acknowledging a tuple lets the spout know that it was processed successfully by downstream components.
+   * **Ack** (transactional topology only): Handles acknowledgments initiated by other components in the topology for tuples sent from the spout. Acknowledging a tuple lets the spout know that it was processed successfully by downstream components.
 
    * **Fail** (transactional topology only): Handles tuples that are fail-processing other components in the topology. Implementing a Fail method allows you to re-emit the tuple so that it can be processed again.
 
@@ -560,7 +561,7 @@ Although it is easy to deploy a topology to a cluster, in some cases, you may ne
 
 1. In **Solution Explorer**, right-click the project, and select **Properties**. In the project properties, change the **Output type** to **Console Application**.
 
-    ![Screenshot of project properties, with Output type highlighted](./media/apache-storm-develop-csharp-visual-studio-topology/outputtype.png)
+    ![Screenshot of project properties, with Output type highlighted](./media/apache-storm-develop-csharp-visual-studio-topology/hdi-output-type-window.png)
 
    > [!NOTE]
    > Remember to change the **Output type** back to **Class Library** before you deploy the topology to a cluster.
@@ -706,7 +707,7 @@ To view errors that have occurred in a running topology, use the following steps
 
 2. For the **Spout** and **Bolts**, the **Last Error** column contains information on the last error.
 
-3. Select the **Spout Id** or **Bolt Id** for the component that has an error listed. On the details page that is displayed, additional error information is listed in the **Errors** section at the bottom of the page.
+3. Select the **Spout ID** or **Bolt ID** for the component that has an error listed. On the details page that is displayed, additional error information is listed in the **Errors** section at the bottom of the page.
 
 4. To obtain more information, select a **Port** from the **Executors** section of the page, to see the Storm worker log for the last few minutes.
 

articles/hdinsight/storm/apache-storm-overview.md

@@ -61,7 +61,7 @@ The Nimbus node provides functionality similar to the Apache Hadoop JobTracker,
 
 The default configuration for Apache Storm clusters is to have only one Nimbus node. Storm on HDInsight provides two Nimbus nodes. If the primary node fails, the Storm cluster switches to the secondary node while the primary node is recovered. The following diagram illustrates the task flow configuration for Storm on HDInsight:
 
-![Diagram of nimbus, zookeeper, and supervisor](./media/apache-storm-overview/nimbus.png)
+![Diagram of nimbus, zookeeper, and supervisor](./media/apache-storm-overview/storm-diagram-nimbus.png)
 
 ## Ease of creation