Adapt FAQ to update code-owners.config to push for review

Direct pushes to refs/meta/config have been disabled at Google, so we
should no longer advertise this.

Change-Id: I74dd509c852ca8c00fbbc581e033e1bd394fdd36
Signed-off-by: Edwin Kempin <ekempin@google.com>

resources/Documentation/config-faqs.md

diff --git a/resources/Documentation/config-faqs.md b/resources/Documentation/config-faqs.md
index fb6226c..c46980b 100644
--- a/resources/Documentation/config-faqs.md
+++ b/resources/Documentation/config-faqs.md
@@ -30,8 +30,9 @@
   refs/meta/config && git checkout FETCH_HEAD`)
 * create or edit the `code-owners.config` file
 * commit the changes
-* push the newly created commit back to the `refs/meta/config` branch (e.g. `git
-  push origin HEAD:refs/meta/config`)
+* push the newly created commit for review to the `refs/meta/config` branch
+  (e.g. `git push origin HEAD:refs/for/refs/meta/config`)
+* get the change approved and submit it
 
 Some of the configuration parameters can also be set via the [Update Code Owner
 Project Config REST endpoint](rest-api.html#update-code-owner-project-config).