Changes asked by Chris

Author: JimDaly

powerapps-docs/developer/data-platform/scalable-customization-design/database-transactions.md

@@ -90,9 +90,9 @@ Before understanding how customizations interact with the platform, it's useful
 |Operation|Description|
 |--|--|
 |Forms (Retrieve)|• Low impact on other uses.|
-|Create|&bull; Performs a create request through the platform<br />&bull; Low impact on other activities, as a new record nothing else blocking on it<br />&bull; Can potentially block locking queries to the whole table until it's complete.<br />&bull; Often can trigger related actions in customization that can have an impact.|
+|Create|&bull; Performs a create request through the platform<br />&bull; Low impact on other activities, as a new record should have nothing else blocking on it.<br />&bull; Can potentially block locking queries to the whole table until it's complete.<br />&bull; Often can trigger related actions in customization that can have an impact.|
 |Update|&bull; Performs an update request through the platform.<br />&bull; More likely to have conflicts. An update lock blocks anything else updating that record.<br />&bull; Often triggers other activities.<br />&bull; In some rare cases, an update lock can block a read lock. One example of where this can occur is when Dataverse metadata is being changed: Reads done by a Dataverse metadata change transaction will be blocked by update locks.|
-|View (RetrieveMultiple)|&bull; Would think this would block lots of other activity.<br />&bull; Although poor query optimization can affect database resource usage and possibly hit timeouts.|
+|View (RetrieveMultiple)|&bull; Low impact on other uses.<br />&bull; Poor performing queries can overwhelm the resources of the database and hit timeouts.|
 
 ## Event pipeline: platform step