Make it clear what last_sync_timestamp actually tracks. Update

chrome/common/webmessageportchannel_impl.cc

Index: chrome/common/webmessageportchannel_impl.cc
diff --git a/chrome/common/webmessageportchannel_impl.cc b/chrome/common/webmessageportchannel_impl.cc
index 86e9a5dc3c2fd5192f62f0e159383945c2fea2db..4ff8b550e7bacf9baa77475639a47270e801f3f9 100644
--- a/chrome/common/webmessageportchannel_impl.cc
+++ b/chrome/common/webmessageportchannel_impl.cc
@@ -152,7 +152,7 @@ void WebMessagePortChannelImpl::Entangle(
 
 void WebMessagePortChannelImpl::QueueMessages() {
   // This message port is being sent elsewhere (perhaps to another process).
-  // The new endpoint needs to recieve the queued messages, including ones that
+  // The new endpoint needs to receive the queued messages, including ones that
   // could still be in-flight.  So we tell the browser to queue messages, and it
   // sends us an ack, whose receipt we know means that no more messages are
   // in-flight.  We then send the queued messages to the browser, which prepends