Update README and OWNERS for the dom/ directory, to reflect new team.

Also fixed one typo I noticed along the way.

Change-Id: Ifd64bf3d8388dcfc2d42ba606d5ecfa786ffa5c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653651
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669062}

third_party/blink/renderer/core/dom/OWNERS

@@ -1,4 +1,4 @@
-hayato@chromium.org
+masonfreed@chromium.org
 
 per-file *_struct_traits*.*=set noparent
 per-file *_struct_traits*.*=file://ipc/SECURITY_OWNERS

third_party/blink/renderer/core/dom/README.md

@@ -730,7 +730,7 @@ DCHECK. :(
 Since `Node::UpdateDistributionForFlatTreeTraversal` can take O(N) in the worst
 case (_even if the distribution flag is clean!_), you should be careful not to
 call it in hot code paths. If you are not sure, please contact
-dom-dev@chromium.org, or add hayato@chromium.org to reviewers.
+dom-dev@chromium.org, or add masonfreed@chromium.org to reviewers.
 
 Once Blink removes Shadow DOM v0 in the future, you don't need to call
 `Node::UpdateDistributionForFlatTreeTraversal` before using `FlatTreeTraversal`

third_party/blink/renderer/core/dom/node.cc

@@ -2816,7 +2816,7 @@ HTMLSlotElement* Node::AssignedSlot() const {
   // in executing RecalcAssignment(), however, unfortunately,
   // that could happen as follows:
   //
-  // 1. RecalsAssignment() can detach a node
+  // 1. RecalcAssignment() can detach a node
   // 2. Then, DetachLayoutTree() may use FlatTreeTraversal via the hook of
   // AXObjectCacheImpl::ChildrenChanged().
   //