Review feedback

Author: FlorianBorn71

articles/remote-rendering/how-tos/conversion/configure-model-conversion.md

@@ -102,7 +102,7 @@ Some source data formats (for example .fbx) provide a unit scaling hint, in whic
 The final scaling factor is applied to the geometry vertices and the local transforms of the scene graph nodes. The scaling for the root entity's transform remains unmodified.
 
 > [!IMPORTANT]
-> Showcase and ARRT tool may compensate for any conversion-time scaling because they have a built-in auto-scaling feature. See also [this entry](../../resources/troubleshoot.md#scaling-value-in-the-conversion-settings-isnt-applied-to-the-model) in the troubleshooting guide.
+> Showcase and Quickstart may compensate for any conversion-time scaling because they have a built-in auto-scaling feature. See also [this entry](../../resources/troubleshoot.md#scaling-value-in-the-conversion-settings-isnt-applied-to-the-model) in the troubleshooting guide.
 
 * `recenterToOrigin` - States that a model should be converted so that its bounding box is centered at the origin.
 If a source model is displaced far from the origin, floating point precision issues may cause rendering artifacts.

articles/remote-rendering/resources/troubleshoot.md

@@ -106,9 +106,10 @@ If these two steps didn't help, it's required to find out whether video frames a
 
 ## Scaling value in the conversion settings isn't applied to the model
 
-If a model shows up in Showcase or ARRT with unchanged scaling albeit a scaling is applied as part of the [conversion settings' geometry parameters](../how-tos/conversion/configure-model-conversion.md#geometry-parameters), then this is probably because of the tool's auto-scaling feature. That is, the tool scales the model for best fit into the view frustum, regardless of its input scaling.
+If a model shows up in Showcase or Quickstart with unchanged scaling albeit a scaling is applied as part of the [conversion settings' geometry parameters](../how-tos/conversion/configure-model-conversion.md#geometry-parameters), then this is probably because of the sample's built-in auto-scaling feature. That is, the sample scales the model for best fit into the view frustum, regardless of its input scaling.
 
-In case of Showcase, auto-scaling can be disabled by specifying a `MaxSize` of zero in the model's `Transform` section inside the models.xml file. This data-driven approach requires that the model is loaded through the xml in the first place, because in all other cases the `MaxSize` defaults to 1 meter. For more information about ways to load models in Showcase, see the [Adding 3D Model Assets to ARR Showcase](https://github.com/Azure/azure-remote-rendering/tree/master/Unity/Showcase/.documents/adding-3d-model-assets-to-application.md) chapter of the Showcase documentation.
+In case of Showcase, auto-scaling can be disabled by specifying a `MaxSize` of zero in the model's `Transform` section inside the models.xml file. This data-driven approach requires that the model is loaded through the XML in the first place, because in all other cases the `MaxSize` defaults to 1 meter. There is also a `MinSize` property which defaults to 0.5 meter, causing all smaller models to be scaled up.
+For more information about ways to load models in Showcase, see the [Adding 3D Model Assets to ARR Showcase](https://github.com/Azure/azure-remote-rendering/tree/master/Unity/Showcase/.documents/adding-3d-model-assets-to-application.md) chapter of the Showcase documentation.
 
 ### Common client-side issues