Fix the output section for point cloud conversions, because it's different there (#120215)

Author: FlorianBorn71

articles/remote-rendering/how-tos/conversion/get-information.md

@@ -1,6 +1,6 @@
 ---
 title: Get information about conversions
-description: Get information about conversions
+description: Get information about conversions.
 author: malcolmtyrrell
 ms.author: matyrr
 ms.date: 03/05/2020
@@ -11,12 +11,12 @@ ms.topic: how-to
 
 ## Information about a conversion: The result file
 
-When the conversion service converts an asset, it writes a summary of any issues into a "result file". 
-For example, if a file `buggy.gltf` is converted, the output container will contain a file called `buggy.result.json`.
+When the conversion service converts an asset, it writes a summary of any issues into a result file. 
+For example, if a file `buggy.gltf` is converted, the output container contains a file called `buggy.result.json`.
 
 The result file lists any errors and warnings that occurred during the conversion and gives a result summary, which is one of `succeeded`, `failed` or `succeeded with warnings`.
 The result file is structured as a JSON array of objects, each of which has a string property that is one of `warning`, `error`, `internal warning`, `internal error`, and `result`. 
-There will be at most one error (either `error` or `internal error`) and there will always be one `result`.
+There is at most one error (either `error` or `internal error`) and there's always one `result`.
 
 ## Example *result* file
 
@@ -36,7 +36,7 @@ However, since there was a missing texture, the resulting arrAsset may not be as
 
 ## Information about a converted model: The info file
 
-The arrAsset file produced by the conversion service is solely intended for consumption by the rendering service. There may be times, however, when you want to access information about a model without starting a rendering session. To support this workflow, the conversion service places a JSON file beside the arrAsset file in the output container. For example, if a file `buggy.gltf` is converted, the output container will contain a file called `buggy.info.json` beside the converted asset `buggy.arrAsset`. It contains information about the source model, the converted model, and about the conversion itself.
+The arrAsset file produced by the conversion service is solely intended for consumption by the rendering service. There may be times, however, when you want to access information about a model without starting a rendering session. To support this workflow, the conversion service places a JSON file beside the arrAsset file in the output container. For example, if a file `buggy.gltf` is converted, the output container contains a file called `buggy.info.json` beside the converted asset `buggy.arrAsset`. It contains information about the source model, the converted model, and about the conversion itself.
 
 ## Example *info* file
 
@@ -106,7 +106,7 @@ Here's an example *info* file produced by converting a file called `buggy.gltf`:
 This section contains the provided filenames.
 
 * `input`: The name of the source file.
-* `output`: The name of the output file, when the user has specified a non-default name.
+* `output`: The name of the output file, when the user has specified a nondefault name.
 
 ### The *conversionSettings* section
 
@@ -128,12 +128,18 @@ It contains the following information:
 * `numOverrides`: The number of override entries read from the material override file.
 * `numOverriddenMaterials`: The number of materials that were overridden.
 
+This section isn't present for point cloud conversions. 
+
 ### The *inputStatistics* section
 
 This section provides information about the source scene. There will often be discrepancies between the values in this section and the equivalent values in the tool that created the source model. Such differences are expected, because the model gets modified during the export and conversion steps.
 
+The content of this section is different for triangular meshes and point clouds.
+
+#### Input statistics for triangular meshes
+
 * `numMeshes`: The number of mesh parts, where each part can reference a single material.
-* `numFaces`: The total number of triangles/points in the whole model. This number contributes to the primitive limit in the [standard rendering server size](../../reference/vm-sizes.md#how-the-renderer-evaluates-the-number-of-primitives).
+* `numFaces`: The total number of triangles in the whole model. This number contributes to the primitive limit in the [standard rendering server size](../../reference/vm-sizes.md#how-the-renderer-evaluates-the-number-of-primitives).
 * `numVertices`: The total number of vertices in the whole model.
 * `numMaterial`: The total number of materials in the whole model.
 * `numFacesSmallestMesh`: The number of triangles/points in the smallest mesh of the model.
@@ -142,6 +148,12 @@ This section provides information about the source scene. There will often be di
 * `numMeshUsagesInScene`: The number of times nodes reference meshes. More than one node may reference the same mesh.
 * `maxNodeDepth`: The maximum depth of the nodes within the scene graph.
 
+#### Input statistics for point clouds
+
+For point cloud conversions, this section contains only a single entry:
+
+* `numPoints`: The total number of points in the input model.
+
 ### The *outputInfo* section
 
 This section records general information about the generated output.
@@ -151,13 +163,22 @@ This section records general information about the generated output.
 
 ### The *outputStatistics* section
 
-This section records information calculated from the converted asset.
+This section records information calculated from the converted asset. Again, the section holds different information for triangular meshes and point clouds.
+
+#### Output statistics for triangular meshes
 
 * `numMeshPartsCreated`: The number of meshes in the arrAsset. It can differ from `numMeshes` in the `inputStatistics` section, because instancing is affected by the conversion process.
 * `numMeshPartsInstanced`: The number of meshes that are reused in the arrAsset.
 * `recenteringOffset`: When the `recenterToOrigin` option in the [ConversionSettings](configure-model-conversion.md) is enabled, this value is the translation that would move the converted model back to its original position.
 * `boundingBox`: The bounds of the model.
 
+#### Output statistics for point clouds
+
+* `numPoints`: The overall number of points in the converted model. This number contributes to the primitive limit in the [standard rendering server size](../../reference/vm-sizes.md#how-the-renderer-evaluates-the-number-of-primitives).
+* `recenteringOffset`: When the `recenterToOrigin` option in the [ConversionSettings](configure-model-conversion.md) is enabled, this value is the translation that would move the converted model back to its original position.
+* `boundingBox`: The bounds of the model.
+
+
 ## Deprecated features
 
 The conversion service writes the files `stdout.txt` and `stderr.txt` to the output container, and these files had been the only source of warnings and errors.