Use term 'folder code owners' instead of 'non-restricted code owners'

The documentation used two different terms to relate to the code owners
that apply to all files in a folder (code owners that are listed without
'per-file' restriction prefix):

1. folder code owners
2. non-restricted code owners

Make this consistent and use always 'folder code owners' which is the
term that is easier to understand.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Icd23972c1df499769a9c166c96c39281b3a31262
1 file changed
tree: af0f245e3d9c050378e74d2afe69b8b93d0cb4ba
  1. java/
  2. javatests/
  3. proto/
  4. resources/
  5. test/
  6. ui/
  7. .eslintrc.json
  8. .gitignore
  9. .gitreview
  10. bower.json
  11. BUILD
  12. LICENSE
  13. package-lock.json
  14. package.json
  15. README.md
README.md

Gerrit Code Review code-owners plugin

This plugin provides support for defining code owners for files in a repository.

If the code-owners plugin is enabled, changes can only be submitted if all touched files are covered by approvals from code owners.

Also see resources/Documentation/about.md.

IMPORTANT: Before installing/enabling the plugin follow the instructions from the setup guide, see resources/Documentation/setup-guide.md.