Doc fixes to contribute for Polygons->Primitives renaming

Author: FlorianBorn71

articles/remote-rendering/overview/features/debug-rendering.md

@@ -30,8 +30,8 @@ void EnableDebugRenderingEffects(RenderingSession session, bool highlight)
     // Enable frame counter text overlay on the server side rendering
     settings.RenderFrameCount = true;
 
-    // Enable polygon count text overlay on the server side rendering
-    settings.RenderPolygonCount = true;
+    // Enable triangle-/point count text overlay on the server side rendering
+    settings.RenderPrimitiveCount = true;
 
     // Enable wireframe rendering of object geometry on the server
     settings.RenderWireframe = true;
@@ -46,8 +46,8 @@ void EnableDebugRenderingEffects(ApiHandle<RenderingSession> session, bool highl
     // Enable frame counter text overlay on the server side rendering
     settings->SetRenderFrameCount(true);
 
-    // Enable polygon count text overlay on the server side rendering
-    settings->SetRenderPolygonCount(true);
+    // Enable triangle-/point count text overlay on the server side rendering
+    settings->SetRenderPrimitiveCount(true);
 
     // Enable wireframe rendering of object geometry on the server
     settings->SetRenderWireframe(true);

articles/remote-rendering/overview/features/performance-queries.md

@@ -120,6 +120,7 @@ Contrary to the `FrameStatistics` object, the `PerformanceAssessment` object con
 | MemoryGPU | Total dedicated video memory utilization in percent of the server GPU |
 | NetworkLatency | The approximate average roundtrip network latency in milliseconds. In the illustration above, this value corresponds to the sum of the red arrows. The value is computed by subtracting actual server rendering time from the `LatencyPoseToReceive` value of `FrameStatistics`. While this approximation is not accurate, it gives some indication of the network latency, isolated from the latency values computed on the client. |
 | PolygonsRendered | The number of triangles rendered in one frame. This number also includes the triangles that are culled later during rendering. That means, this number does not vary a lot across different camera positions, but performance can vary drastically, depending on the triangle culling rate.|
+| PointsRendered | The number of points in point clouds rendered in one frame. Same culling criteria as mentioned above for `PolygonsRendered` apply here.|
 
 To help you assess the values, each portion comes with a quality classification like **Great**, **Good**, **Mediocre**, or **Bad**.
 This assessment metric provides a rough indication of the server's health, but it should not be seen as absolute. For example, assume you see a 'mediocre' score for the GPU time. It is considered mediocre because it gets close to the limit for the overall frame time budget. In your case however, it might be a good value nonetheless, because you are rendering a complex model.

articles/remote-rendering/reference/vm-sizes.md

@@ -73,7 +73,7 @@ For the [example PowerShell scripts](../samples/powershell-example-scripts.md),
 
 ### How the renderer evaluates the number of primitives
 
-The number of primitives that are considered for the limitation test are the number of primitives that are actually passed to the renderer. This geometry is typically the sum of all instantiated meshes, but there are also exceptions. The following geometry is **not included**:
+The number of primitives that are considered for the limitation test are the number of primitives (triangles and points) that are actually passed to the renderer. This geometry is typically the sum of all instantiated meshes, but there are also exceptions. The following geometry is **not included**:
 * Loaded model instances that are fully outside the view frustum.
 * Models or model parts that are switched to invisible, using the [hierarchical state override component](../overview/features/override-hierarchical-state.md).
 
@@ -83,7 +83,7 @@ Accordingly, it's possible to write an application that targets the `standard` s
 
 There are two ways to determine the number of primitives of a model or scene that contribute to the budget limit of the `standard` configuration size:
 * On the model conversion side, retrieve the [conversion output json file](../how-tos/conversion/get-information.md), and check the `numFaces` entry in the [*inputStatistics* section](../how-tos/conversion/get-information.md#the-inputstatistics-section). This number denotes the triangle count in triangular meshes and number of points in point clouds respectively.
-* If your application is dealing with dynamic content, the number of rendered primitives can be queried dynamically during runtime. Use a [performance assessment query](../overview/features/performance-queries.md#performance-assessment-queries) and check for the `polygonsRendered` member in the `FrameStatistics` struct. The `PolygonsRendered` field will be set to `bad` when the renderer hits the primitive limitation. The checkerboard background is always faded in with some delay to ensure user action can be taken after this asynchronous query. User action can, for instance,  be hiding or deleting model instances.
+* If your application is dealing with dynamic content, the number of rendered primitives can be queried dynamically during runtime. Use a [performance assessment query](../overview/features/performance-queries.md#performance-assessment-queries) and check for the sum of the values in the two members `PolygonsRendered` and `PointsRendered` in the `PerformanceAssessment` struct. The `PolygonsRendered` / `PointsRendered` field will be set to `bad` when the renderer hits the primitive limitation. The checkerboard background is always faded in with some delay to ensure user action can be taken after this asynchronous query. User action can, for instance,  be hiding or deleting model instances.
 
 ## Pricing