diff --git a/docs/source/content_generator_metadata.rst b/docs/source/content_generator_metadata.rst
index ef3df700..e878ef6d 100644
--- a/docs/source/content_generator_metadata.rst
+++ b/docs/source/content_generator_metadata.rst
@@ -21,7 +21,7 @@ The map has four top-level entries:
 -  buildroots: A list of maps, one for each environment in which build
    output was generated, containing information about that environment.
 -  output: A list of maps, one map for each file that will be imported
-   and managed by Brew.
+   and managed by Koji.
 
 metadata\_version
 -----------------
diff --git a/docs/source/content_generators.rst b/docs/source/content_generators.rst
index ecf13232..c54575d6 100644
--- a/docs/source/content_generators.rst
+++ b/docs/source/content_generators.rst
@@ -36,7 +36,7 @@ that those policies are followed before the content generator is granted
 authorization in their Koji system.
 
 Below are some examples of the sorts of policies that one might require.
-Content Generators should be designed and implemented with the
+Content Generators should be designed and implemented with these
 requirements in mind. Please note that the list below is not complete.
 
 Avoid Using the Host's Software