Merge pull request #286427 from MicrosoftDocs/main

9/10 11:00 AM IST Publish

Author: PhilKang0704

articles/databox/data-box-system-requirements.md

@@ -6,8 +6,8 @@ author: stevenmatthew
 
 ms.service: databox
 ms.subservice: pod
-ms.topic: article
-ms.date: 09/09/2024
+ms.topic: conceptual
+ms.date: 10/21/2022
 ms.author: shaas
 ---
 
@@ -17,8 +17,10 @@ This article describes important system requirements for your Microsoft Azure Da
 
 The system requirements include:
 
-* **Software requirements:** For hosts that connect to the Data Box, describes supported operating systems, file transfer protocols, storage accounts, storage types, and browsers for the local web UI.
-* **Networking requirements:** For the Data Box, describes requirements for network connections and ports for best operation of the Data Box.
+* **Software requirements** for hosts that connect to Data Box.<br>
+They describe supported operating systems, file transfer protocols, storage accounts, storage types, and browsers for the local web UI.
+* **Networking requirements** for the Data Box device.<br>
+They describe network connections and ports used for optimal Data Box device operation.
 
 
 ## Software requirements
@@ -34,8 +36,10 @@ The software requirements include supported operating systems, file transfer pro
 [!INCLUDE [data-box-supported-file-systems-clients](../../includes/data-box-supported-file-systems-clients.md)]
 
 > [!IMPORTANT]
-> Connection to Data Box shares is not supported via REST for export orders. 
-> Transporting data from on-premises NFS clients into Data Box using NFSv4 is supported. However, to copy data from Data Box to Azure, Data Box supports only REST-based transport. Azure file share with NFSv4.1 does not support REST for data access/transfers.
+> Connection to Data Box shares is not supported via REST for export orders.
+>
+> You can transport your data to Data Box from on-premises Network File System (NFS) clients by using NFSv4. However, when copying data from Data Box to Azure, Data Box supports REST-based transport only. Azure file shares with NFSv4.1 doesn't support REST for data access or transfer.
+
 ### Supported storage accounts
 
 > [!Note]
@@ -57,7 +61,7 @@ Your datacenter needs to have high-speed network. We strongly recommend you have
 
 ### Port requirements
 
-The following table lists the ports that need to be opened in your firewall to allow for SMB or NFS traffic. In this table, *In* (*inbound*) refers to the direction from which incoming client requests access to your device. *Out* (or *outbound*) refers to the direction in which your Data Box device sends data externally, beyond the deployment. For example, data might be outbound to the Internet.
+The following table lists the ports that need to be opened in your firewall to allow for Server Message Block (SMB) or  Network File System (NFS) traffic. In this table, *In* (*inbound*) refers to the direction from which incoming client requests access to your device. *Out* (or *outbound*) refers to the direction in which your Data Box device sends data externally, beyond the deployment. For example, data might be outbound to the Internet.
 
 [!INCLUDE [data-box-port-requirements](../../includes/data-box-port-requirements.md)]
 

articles/governance/resource-graph/changes/get-resource-changes.md

@@ -53,8 +53,6 @@ When a resource is created, updated, or deleted, a new change resource (`Microso
     "properties.provisioningState": {
       "newValue": "Succeeded",
       "previousValue": "Updating",
-      "changeCategory": "System",
-      "propertyChangeType": "Update",
       "isTruncated": "true"
     },
     "tags.key1": {

articles/hdinsight/kafka/apache-kafka-get-started.md

@@ -199,10 +199,10 @@ Kafka stores streams of data in *topics*. You can use the `kafka-topics.sh` util
 * **To create a topic**, use the following command in the SSH connection:
 
     ```bash
-    /usr/hdp/current/kafka-broker/bin/kafka-topics.sh --create --replication-factor 3 --partitions 8 --topic test --zookeeper $KAFKAZKHOSTS
+    /usr/hdp/current/kafka-broker/bin/kafka-topics.sh --create --replication-factor 3 --partitions 8 --topic test --bootstrap-server $KAFKABROKERS
     ```
 
-    This command connects to Zookeeper using the host information stored in `$KAFKAZKHOSTS`. It then creates an Apache  Kafka topic named **test**.
+    This command connects to Broker using the host information stored in `$KAFKABROKERS`. It then creates an Apache  Kafka topic named **test**.
 
     * Data stored in this topic is partitioned across eight partitions.
 
@@ -227,15 +227,15 @@ Kafka stores streams of data in *topics*. You can use the `kafka-topics.sh` util
 * **To list topics**, use the following command:
 
     ```bash
-    /usr/hdp/current/kafka-broker/bin/kafka-topics.sh --list --zookeeper $KAFKAZKHOSTS
+    /usr/hdp/current/kafka-broker/bin/kafka-topics.sh --list --bootstrap-server $KAFKABROKERS
     ```
 
     This command lists the topics available on the Apache Kafka cluster.
 
 * **To delete a topic**, use the following command:
 
     ```bash
-    /usr/hdp/current/kafka-broker/bin/kafka-topics.sh --delete --topic topicname --zookeeper $KAFKAZKHOSTS
+    /usr/hdp/current/kafka-broker/bin/kafka-topics.sh --delete --topic topicname --bootstrap-server $KAFKABROKERS
     ```
 
     This command deletes the topic named `topicname`.

articles/hpc-cache/media/hpc-cache-mount-addresses.png

@@ -266,10 +266,10 @@ You're now ready to run the device code and the service code that initiates a re
 
    The following shows the device response to the reboot direct method:
 
-   ![Simulated device app output](./media/iot-hub-python-python-device-management-get-started/device.png)
+   ![Screenshot that shows the output of the simulated device app after receiving reboot direct method.](./media/device-management-python/device.png)
 
    The following shows the service calling the reboot direct method and polling the device twin for status:
 
-   ![Trigger reboot service output](./media/iot-hub-python-python-device-management-get-started/service.png)
+   ![Screenshot that shows the output of the service app after sending reboot direct method.](./media/device-management-python/service.png)
 
 [!INCLUDE [iot-hub-dm-followup](../../includes/iot-hub-dm-followup.md)]