make branding

RedHatSatellite · Jun 23, 2021 · 1b1e755 · 1b1e755
1 parent c1d9aef
commit 1b1e755
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/_gh_include/header.inc b/docs/_gh_include/header.inc
@@ -1,7 +1,7 @@
 <!doctype html>
 <html>
   <head>
-  <title>Foreman Ansible Modules documentation index</title>
+  <title>Red Hat Satellite Ansible Collection documentation index</title>
   <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <link rel="stylesheet" media="all" href="https://theforeman.org/static/css/bootstrap.min.css"/>
   <link rel="stylesheet" media="all" href="https://theforeman.org/static/css/bootstrap-responsive.min.css"/>
@@ -10,7 +10,7 @@
   </head>
 
   <body style="margin:0px 15px">
-    <h1>Foreman Ansible Modules</h1>
+    <h1>Red Hat Satellite Ansible Collection</h1>
 
     <hr />
 

diff --git a/roles/repositories/README.md b/roles/repositories/README.md
@@ -12,7 +12,7 @@ This role supports the [Common Role Variables](https://github.com/theforeman/for
   Each product is represented as a dictionary and can include `repository_sets` which represent Red Hat Repositories and should be used when the product name matches an existing Red Hat Product.
   Each element of `repository_sets` must have a `name` and should specify the `basearch` and/or `releasever` only when multiple versions are available for that Product.
   All repository sets for a Red Hat Product can be enabled by omitting `repository_sets` and instead specifying that the Product has `all_repositories: True`. When using this option it is also necessary to specify a list of repository `label`s for the Product (e.g. rhel-7-server-rpms). Be wary that this option can result in enabling a large number of unused repositories that, if added to sync plans, can greatly increase sync times and rapidly fill disk space.
-  Custom (i.e. non Red Hat) Products can also be defined, with associated `repositories` which represent custom repositories, and are required to have a `name`, `url`, and `content_type`; they may require additional fields and can take any parameter supported by [redhat.satellite.repository](https://theforeman.github.io/foreman-ansible-modules/develop/plugins/repository_module.html).
+  Custom (i.e. non Red Hat) Products can also be defined, with associated `repositories` which represent custom repositories, and are required to have a `name`, `url`, and `content_type`; they may require additional fields and can take any parameter supported by [redhat.satellite.repository](https://redhatsatellite.github.io/satellite-ansible-collection/develop/plugins/repository_module.html).
   A variety of examples are demonstrated in the data structure below:
 
 ```yaml