Fix typo in code review documentation.

docs/code_reviews.md

 # Code Reviews
 
 Code reviews are a central part of developing high-quality code for Chromium.
 All changes must be reviewed.
 
 The bigger patch-upload-and-land process is covered in more detail the
 [contributing code](https://www.chromium.org/developers/contributing-code)
 page.
 
 # Code review policies
@@ skipping 154 matching lines @@
 # You can include comments like this.
 a@chromium.org
 b@chromium.org  # Only for the frobinator.
 ```
 
 A `*` indicates that all committers are owners:
 ```
 *
 ```
 
-The text `set noparent` it will stop owner propagation from parent directories.
+The text `set noparent` will stop owner propagation from parent directories.
 This is used for specialized code. In this example, only the two listed people
 are owners:
 ```
 set noparent
 a@chromium.org
 b@chromium.org
 ```
 
 The `per-file` directive allows owners to be added that apply only to files
 matching a pattern. In this example, owners from the parent directiory
 apply, plus one person for some classes of files, and all committers are
 owners for the readme:
 ```
 per-file foo_bar.cc=a@chromium.org
 per-file foo.*=a@chromium.org
 
 per-file readme.txt=*
 ```
 
 Other `OWNERS` files can be included by reference by listing the path to the
 file with `file://...`. This example indicates that only the people listed in
 `//ipc/SECURITY_OWNERS` can review the messages files:
 ```
 per-file *_messages*.h=set noparent
 per-file *_messages*.h=file://ipc/SECURITY_OWNERS
 ```