Fix references to ResetAndReturn in docs.

Bug: none
Change-Id: Iadcb1b111922a417e09293e2e73bec7b464e9c13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869031
Commit-Queue: David Benjamin <davidben@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707375}

net/docs/code-patterns.md

@@ -210,7 +210,7 @@ The characteristics of the DoLoop pattern are:
                result = DoLoop(result);
 
                if (result != ERR_IO_PENDING && !callback_.is_null())
-                 base::ResetAndReturn(&callback_).Run(result);
+                 std::move(callback_).Run(result);
              }
     
 *   The DoLoop pattern has no concept of different events arriving for

net/docs/life-of-a-feature.md

@@ -224,8 +224,7 @@ callback may result in the deletion of the current (calling) object. As
 further expanded upon in [Code Patterns](code-patterns.md), features and
 changes should be designed such that any callback invocation is the last
 bit of code executed, and that the callback is accessed via the stack (such
-as through the use of either `base::ResetAndReturn(callback_).Run()` or
-`std::move(callback_).Run()`.
+as through the use of `std::move(callback_).Run()`.
 
 ### Specs: What Are They Good For