Updates to README-type files

Author: mjang

CODE_OF_CONDUCT.md

@@ -74,3 +74,5 @@ This Code of Conduct is adapted from the [Contributor Covenant](https://www.cont
 
 Community Impact Guidelines were inspired by
 [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/inclusion).
+
+For answers to common questions about this code of conduct, see the FAQ at <https://www.contributor-covenant.org/faq>. Translations are available at <https://www.contributor-covenant.org/translations>.

F5-NGINX-team-notes.md

@@ -6,11 +6,13 @@ public repository. However, if you are working with:
 - Security content, including personally identifying information (PII).
 - Content / features that are not yet ready to be announced.
 
-Make changes to the `docs-internal` repository. When you create a branch, start it with:
+Make changes to the private `docs` repository. When you create a branch, start it with:
 `internal/`. 
 
-- The public `docs` repository will reject branches that start with `internal/`.
-- The `docs-internal` repository will accept branches _only_ if it includes `internal/`.
+- The public `documentation` repository will reject branches that start with `internal/`.
+- The `docs` repository will accept branches _only_ if it includes `internal/`.
+
+Before new content is published, it must be written to the open `documentation` repository. After you get approvals in the internal `docs` repository, you'll need to create a _second_ pull request in the open `documentation` repository.
 
 If you need to review a pull request and are an employee of F5/NGINX, ask a member of @nginx/nginx-docs for help.