Merge pull request MicrosoftDocs#3262 from MicrosoftDocs/matp-richtextcontrol

Matp richtextcontrol

Author: Mattp123

powerapps-docs/maker/model-driven-apps/rich-text-editor-control.md

@@ -111,16 +111,12 @@ By setting this property, you can avoid using the default entity for images so t
 
 ### disableImages
 
-Set this property to false will enable images. This property will have highest priority. This means that when this property is set to true, irrespective of the *imageEntity* property value, images will be disabled. By default, images are disabled.
+Set this property to true will disable images. This property will have highest priority. This means that when this property is set to true, irrespective of the [imageEntity](#imageentity) property value, images will be disabled. By default, images are enabled.
 
 ### disableDefaultImageProcessing
 
 By default, images will be uploaded using the client API. As soon as an image gets added to the editor, it will be uploaded to the platform. To process images, set this property to true.
 
-### Storing images
-
-The rich text editor control default behavior stores images as Base64. Base64 images require large amount of space and most existing fields might not have sufficient space. When the limit is exceeded, the message "You have exceeded the maximum number of 2000 characters in this field" is displayed in the app. To avoid this problem, as soon as an image gets added to the editor, it will be uploaded to the blob store using the pre-configured API and Base64 content will be replaced with platform URL.
-
 ## Sample rich text editor configuration file
 
 The following sample sets the several options in the rich text editor such as the height, location, default font type, and uses plugin logic. For more information about plugins, see [Use plug-ins to extend business processes](../../developer/common-data-service/plug-ins.md).
@@ -152,7 +148,7 @@ The following sample sets the several options in the rich text editor such as th
 
 ## Known issue
 
-HTML markup is displayed in the field configured to use the rich text editor control when the field is part of a subgrid.
+HTML markup is displayed for fields configured to use the rich text editor control that are displayed in components other than a field on a form. For example, this occurs in views, subgrids, paginated reports, and portals.
 > [!div class="mx-imgBorder"] 
 > ![HTML markup displayed in a field on a subgrid.](media/html-markup-issue.png)