Spellfix: poitner -> pointer.

No logic changes.

Change-Id: I3f35d7e149f6ffef9cc561c57250eeeacdf603f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973193
Commit-Queue: Stefan Zager <szager@chromium.org>
Auto-Submit: Darwin Huang <huangdarwin@chromium.org>
Reviewed-by: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726104}

content/renderer/input/input_event_prediction.h

@@ -53,7 +53,7 @@ class CONTENT_EXPORT InputEventPrediction {
   // UpdateSinglePointer for each pointer.
   void UpdatePrediction(const WebInputEvent& event);
   // Cast events from WebInputEvent to WebPointerProperties. Call
-  // ResamplingSinglePointer for each poitner.
+  // ResamplingSinglePointer for each pointer.
   void ApplyResampling(base::TimeTicks frame_time, WebInputEvent* event);
   // Reset predictor for each pointer in WebInputEvent by  ResetSinglePredictor.
   void ResetPredictor(const WebInputEvent& event);

docs/memory/tools.md

@@ -147,7 +147,7 @@ looking similar due to the nature of DOM node allocation.
 ### Instructions
 #### <a name="configure-oophp"></a>Configuration and setup
   1. [Android Only] For native stack traces, a custom build with
-     `enable_framepoitners=true` is required.
+     `enable_framepointers=true` is required.
   2. Configure OOPHP settings in about://flags. (See table below)
   3. Restart browser with new settings if necessary.
   4. Verify target processes are being profiled in chrome://memory-internals.