address reviewer comments

hansgschossmann · hansgschossmann · commit 2bce18bb5e15 · 2022-01-21T15:55:46.000+01:00
diff --git a/articles/industrial-iot/overview-what-is-industrial-iot.md b/articles/industrial-iot/overview-what-is-industrial-iot.md
@@ -18,7 +18,7 @@ Microsoft Azure Industrial Internet of Things (IIoT) is a suite of Azure cloud m
 
 The Azure Industrial IoT Platform allows plant operators to discover OPC UA-enabled servers in a factory network and register them in Azure IoT Hub. Operations personnel can subscribe and react to events on the factory floor from anywhere in the world. Azure IIoT will enable the reception of alerts and alarms, and will allow reaction to them in real time.
 
-Azure IIoT provides a set of microservices that connect to OPC UA systems on the shop floor. The microservices REST APIs mirrors the OPC UA systems functionality. The REST APIs enable your cloud applications to browse OPC UA server address spaces, read/write values of OPC UA nodes, and execute OPC UA methods. Components at the factory floor are implemented as Azure IoT Edge modules. The cloud microservices are ASP.NET microservices with a REST interface and run on managed Azure Kubernetes Services or standalone on Azure App Service. Azure IoT Edge modules and Azure IIoT cloud services are available as pre-built Docker containers in the Microsoft Container Registry (MCR).
+Azure IIoT provides a set of microservices that connect to OPC UA systems on the shop floor. The microservices REST APIs mirror the OPC UA systems functionality. The REST APIs enable your cloud applications to browse OPC UA server address spaces, read/write values of OPC UA nodes, and execute OPC UA methods. Components at the factory floor are implemented as Azure IoT Edge modules. The cloud microservices are ASP.NET microservices with a REST interface and run on managed Azure Kubernetes Services or standalone on Azure App Service. Azure IoT Edge modules and Azure IIoT cloud services are available as pre-built Docker containers in the Microsoft Container Registry (MCR).
 
 The edge modules and cloud services collaborate closely and must be used together. Azure IIoT provides easy-to-use deployment scripts that allow to deploy the entire platform with a single command.
 
@@ -30,37 +30,42 @@ Azure Industrial IoT manages OPC UA Application Certificates and Trust Lists of
 
 ## Industrial IoT Components
 
-Azure IIoT solutions are built from specific components. These components include the following:
+Azure IIoT solutions are built from specific components:
 
 - **At least one Azure IoT Hub.**
 - **IoT Edge devices.**
 - **Industrial Edge Modules.**
 
 ### IoT Hub
-The [Azure IoT Hub](https://azure.microsoft.com/services/iot-hub/) acts as a central message hub for secure, bi-directional communications between any IoT application and the devices it manages. It's an open and flexible cloud platform as a service (PaaS) that supports open-source SDKs and multiple protocols. 
+
+The [Azure IoT Hub](https://azure.microsoft.com/services/iot-hub/) acts as a central message hub for secure, bi-directional communications between any IoT application and the devices it manages. It's an open and flexible cloud platform as a service (PaaS) that supports open-source SDKs and multiple protocols.
 
 Gathering your industrial and business data onto an IoT Hub lets you store your data securely, perform business and efficiency analyses on it, and generate reports from it. You can also apply Microsoft Azure services and tools, such as [Power BI](https://powerbi.microsoft.com), on your combined data.
 
 ### IoT Edge devices
+
 The [edge services](https://azure.microsoft.com/services/iot-edge/) are implemented as Azure IoT Edge modules and run on-premises. The cloud microservices are implemented as ASP.NET microservices with a REST interface and run on managed Azure Kubernetes Services or stand-alone on Azure App Service. For both edge and cloud services, we have provided pre-built Docker containers in the Microsoft Container Registry (MCR), removing this step for the customer. The edge and cloud services are applying each other and must be used together. We have also provided easy-to-use deployment scripts that allow one to deploy the entire platform with a single command.
 
 An IoT Edge device is composed of an IoT Edge Runtime and IoT Edge Modules.
-- **Edge Modules** are docker containers, which are the smallest unit of computation, like OPC Publisher and OPC Twin. 
+
+- **Edge Modules** are docker containers, which are the smallest unit of computation, like OPC Publisher and OPC Twin.
 - **Edge device** is used to deploy such modules, which act as mediator between OPC UA server and IoT Hub in cloud.
 
 ### Industrial IoT Edge Modules
+
 - **OPC Publisher**: The OPC Publisher module connects to OPC UA server systems and publishes JSON encoded telemetry data from these servers in OPC UA "Pub/Sub" format to Azure. The OPC Publisher can run in two modes:
   - In combination with and controlled by the Industrial-IoT cloud microservices (orchestrated mode)
-  - Configured by a local configuration file to allow operation without any Industrial-IoT cloud microservice (standalone mode) 
-- **OPC Twin**: The OPC Twin module enables connection from the cloud to OPC UA server systems on the factory network. OPC Twin provides access to OPC UA server systems through REST APIs exposed by the Industrial-IoT cloud microservices. 
+  - Configured by a local configuration file to allow operation without any Industrial-IoT cloud microservice (standalone mode)
+- **OPC Twin**: The OPC Twin module enables connection from the cloud to OPC UA server systems on the factory network. OPC Twin provides access to OPC UA server systems through REST APIs exposed by the Industrial-IoT cloud microservices.
 - **Discovery**: The Discovery module works only in combination with the Industrial-IoT cloud microservices. The Discovery module implements OPC UA server system discovery and reports the results to the Industrial-IoT cloud microservices.
- 
 
 ## Next steps
+
 Now that you have learned what Industrial IoT is, you can read more about the OPC Publisher or get started with deploying the IIoT Platform:
 
 > [!div class="nextstepaction"]
 > [What is the OPC Publisher?](overview-what-is-opc-publisher.md)
 
 > [!div class="nextstepaction"]
-> [Deploy the Industrial IoT Platform](tutorial-deploy-industrial-iot-platform.md)
+> [Deploy the Industrial IoT Platform](tutorial-deploy-industrial-iot-platform.md)
+>
diff --git a/articles/industrial-iot/tutorial-publisher-configure-opc-publisher.md b/articles/industrial-iot/tutorial-publisher-configure-opc-publisher.md
@@ -15,6 +15,7 @@ In this tutorial contains information on the configuration of the OPC Publisher.
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
+>
 > * Configure the OPC Publisher via Configuration File
 > * Configure the OPC Publisher via Command-line Arguments
 > * Configure the OPC Publisher via IoT Hub Direct Methods
@@ -26,14 +27,16 @@ IoT Edge provides OPC Publisher with its security configuration for accessing Io
 
 To access OPC UA systems, X.509 certificates are used by OPC UA. The certificates are used for authentication and encryption of the data exchanged. OPC Publisher uses a file system-based certificate store to manage all application certificates. During startup, OPC Publisher checks existence of its own certificate in the certificate store. If no certificate exists for OPC Publisher, it creates a new self-signed certificate and associated private key. Self-signed certificates provide weak authentication, since they are not signed by a trusted Certificate Authority.
 
-Security is enabled in the configuration file via the `"UseSecurity": true,` flag. The most secure endpoint available on the OPC UA servers the OPC Publisher is supposed to connect to is automatically selected.
-By default, OPC Publisher uses anonymous user authentication (in extra to the application authentication described above). However, OPC Publisher also supports user authentication using username and password. These credentials can be specified via the REST API configuration interface (described below) or the configuration file as follows:
-```
+Security is enabled in the configuration file via the `"UseSecurity": true,` flag. The most secure endpoint available on the OPC UA server the OPC Publisher is supposed to connect to is automatically selected.
+By default, OPC Publisher uses anonymous user authentication (in addition to the application authentication described above). However, OPC Publisher also supports user authentication using username and password. These credentials can be specified via the REST API configuration interface (described below) or the configuration file as follows:
+
+```json
 "OpcAuthenticationMode": "UsernamePassword",
 "OpcAuthenticationUsername": "usr",
 "OpcAuthenticationPassword": "pwd",
 ```
-OPC Publisher version 2.5 and below encrypts the username and password in the configuration file. Version 2.6 and above only supports the username and password in plaintext. 
+
+OPC Publisher version 2.5 and below encrypts the username and password in the configuration file. Version 2.6 and above only supports the username and password in plaintext.
 
 To persist the security configuration of OPC Publisher, the certificate store must be mapped to the IoT Edge host OS filesystem or a container data volume.
 
@@ -43,7 +46,8 @@ The simplest way to configure OPC Publisher is via a configuration file. An exam
 Configuration file syntax has changed over time. OPC Publisher still can read old formats, but converts them into the latest format when writing the file.
 
 A basic configuration file looks like this:
-```
+
+```json
 [
   {
     "EndpointUrl": "opc.tcp://testserver:62541/Quickstarts/ReferenceServer",
@@ -61,16 +65,18 @@ A basic configuration file looks like this:
 ```
 
 OPC UA server systems optimize network bandwidth by only sending data changes to OPC Publisher when the data has changed. If data changes need to be published more often or at regular intervals, OPC Publisher supports a "heartbeat" setting for every configured OPC UA node. This "heartbeat" can be enabled by specifying the `HeartbeatInterval` key in the node configuration. The interval is specified in seconds:
-```
+
+```json
  "HeartbeatInterval": 3600,
 ```
 
 An OPC UA server system always sends the current value of a node when OPC Publisher connects to it. To prevent publishing this data to the cloud, the `SkipFirst` key can be additionally specified in the node configuration:
-```
+
+```json
  "SkipFirst": true,
 ```
 
->[!NOTE] 
+>[!NOTE]
 > This feature is only available in version 2.5 and below of OPC Publisher.
 
 Both settings can be enabled globally via command-line options, too.
@@ -79,54 +85,54 @@ Both settings can be enabled globally via command-line options, too.
 
 There are [several command-line arguments](reference-command-line-arguments.md) that can be used to set global settings for OPC Publisher.
 
-
 ## Configuration via the built-in OPC UA Server Interface
 
->[!NOTE] 
+>[!NOTE]
 > This feature is only available in version 2.5 and below of OPC Publisher.
 
 OPC Publisher has a built-in OPC UA server, running on port 62222. It implements three OPC UA methods:
 
-  - PublishNode
-  - UnpublishNode
-  - GetPublishedNodes
+* PublishNode
+* UnpublishNode
+* GetPublishedNodes
 
 This interface can be accessed using an OPC UA client application, for example [UA Expert](https://www.unified-automation.com/products/development-tools/uaexpert.html).
 
 ## Configuration via IoT Hub Direct Methods
 
->[!NOTE] 
+>[!NOTE]
 > This feature is only available in version 2.5 and below of OPC Publisher.
 
 OPC Publisher implements the following [IoT Hub Direct Methods](../iot-hub/iot-hub-devguide-direct-methods.md), which can be called from an application (from anywhere in the world) using the [IoT Hub Device SDK](../iot-hub/iot-hub-devguide-sdks.md):
 
-  - PublishNodes
-  - UnpublishNodes
-  - UnpublishAllNodes
-  - GetConfiguredEndpoints
-  - GetConfiguredNodesOnEndpoint
-  - GetDiagnosticInfo
-  - GetDiagnosticLog
-  - GetDiagnosticStartupLog
-  - ExitApplication
-  - GetInfo
+* PublishNodes
+* UnpublishNodes
+* UnpublishAllNodes
+* GetConfiguredEndpoints
+* GetConfiguredNodesOnEndpoint
+* GetDiagnosticInfo
+* GetDiagnosticLog
+* GetDiagnosticStartupLog
+* ExitApplication
+* GetInfo
 
 ## Configuration via Cloud-based, Companion REST Microservice
 
->[!NOTE] 
+>[!NOTE]
 > This feature is only available in version 2.6 and above of OPC Publisher.
 
 A cloud-based, companion microservice with a REST interface is described and available [here](https://github.com/Azure/Industrial-IoT/blob/main/docs/services/publisher.md). It can be used to configure OPC Publisher via an OpenAPI-compatible interface, for example through Swagger.
 
 ## Configuration of the simple JSON telemetry format via Separate Configuration File
 
->[!NOTE] 
+>[!NOTE]
 > This feature is only available in version 2.5 and below of OPC Publisher.
 
 OPC Publisher allows configuration of the simple telemetry format via a configuration file. This file can be specified via the `--tc`  command-line option. By default the full JSON telemetry format is sent to IoT Hub. The format of the telemetry configuration file is described [here](reference-opc-publisher-telemetry-format.md#opc-publisher-telemetry-configuration-file-format).
 
 ## Next steps
-After successful configuration of OPC Publisher, the next step is to learn how to tune the performance and memory of the module:
+
+After a successful configuration of OPC Publisher, the next step is to learn how to tune the performance and memory of the module:
 
 > [!div class="nextstepaction"]
 > [Performance and Memory Tuning](tutorial-publisher-performance-memory-tuning-opc-publisher.md)
