Visual logging for Application > Manifest

Bug: b/308381403
Change-Id: I9accfde8183eb6090ada240d8dd32aca68b267f3
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5126352
Commit-Queue: Kateryna Prokopenko <[email protected]>
Auto-Submit: Kateryna Prokopenko <[email protected]>
Reviewed-by: Danil Somsikov <[email protected]>
diff --git a/docs/visual_logging.md b/docs/visual_logging.md
index f459d06..404717b 100644
--- a/docs/visual_logging.md
+++ b/docs/visual_logging.md
@@ -1,7 +1,7 @@
 # Visual logging
 
 The goal of this project is to improve the logging of user interactions in
-DevTools. The current UMA logging is unreliable and inconsistent. This can lead
+DevTools. The current UMA logging is unreliable and inconsistent. This can lead to
 incorrect conclusions about how users are interacting with the product.
 
 We want to be able to understand how users are interacting with DevTools so that
@@ -90,7 +90,7 @@
 can be a string or a number. If a string is given, it is be first considered
 to refer to a context provider (see below). If no context provider is registered
 with this name, SHA-1 hash is computed and the first 32 bits
-(little endian) is logged. Number is be logged as is.
+(little endian) is logged. Number will be logged as is.
 
 The `parent()` method sets the custom parent provider for the visual logging element
 (see below). If not invoked, the parent visual element is taken from a DOM tree structure.