Merge pull request #386 from michellemacrh/github-385-pr

github-385-pr: Add Ansible Rulebook to glossary

Author: bburt-rh

supplementary_style_guide/glossary_terms_conventions/general_conventions/a.adoc

@@ -328,8 +328,8 @@ _Valid values are `amd64`._
 // RHEL: General; kept as is
 [[ansible-playbook]]
 ==== image:images/yes.png[yes] Ansible Playbook (noun)
-*Description*: Playbooks are Ansible’s configuration, deployment, and orchestration language.
-Playbooks can describe a policy you want your remote systems to enforce, or a set of steps in a general IT process.
+*Description*: Playbooks are the configuration, deployment, and orchestration language for Ansible Automation Platform.
+Playbooks can describe a policy you want your remote systems to enforce or a set of steps in a general IT process.
 An _Ansible Playbook_ is a file that contains one or more Ansible plays.
 Write as shown: uppercase _A_ and uppercase _P_. When using the term _playbook_ without the Ansible prefix, use lowercase _p_.
 
@@ -342,7 +342,22 @@ Examples:
 
 *Incorrect forms*: Ansible playbook
 
-*See also*: xref:ansible-play[Ansible play]
+*See also*: xref:ansible-play[Ansible play], xref:playbook[playbook]
+
+[[ansible-rulebook]]
+==== image:images/yes.png[yes] Ansible Rulebook (noun)
+*Description*: An _Ansible Rulebook_ tells Event-Driven Ansible which sources to monitor for an event and what to do when certain conditions are met. Rulebooks are written in YAML and are used like Ansible Playbooks. Write as shown: uppercase _A_ and uppercase _R_. When using the term "rulebook" without the Ansible prefix, use lowercase _r_.
+
+Examples:
+
+* Use a rulebook in Ansible.
+* Use an Ansible Rulebook.
+
+*Use it*: yes
+
+*Incorrect forms*: Ansible rulebook
+
+*See also*: xref:rulebook[rulebook]
 
 // RHEL: General; kept as is
 [[ansible-task]]

supplementary_style_guide/glossary_terms_conventions/general_conventions/p.adoc

@@ -228,6 +228,23 @@ When combined with privileges, permissions define a user's or resource's overall
 
 *See also*:
 
+[[playbook]]
+==== image:images/yes.png[yes] playbook (noun)
+*Description*: _Playbooks_ are the configuration, deployment, and orchestration language for Ansible Automation Platform.
+Playbooks can describe a policy you want your remote systems to enforce or a set of steps in a general IT process.
+When using the term "playbook" without the Ansible prefix, use lowercase _p_.
+
+Examples:
+
+* Run a playbook in Ansible.
+* Run an Ansible Playbook.
+
+*Use it*: yes
+
+*Incorrect forms*: Playbook
+
+*See also*: xref:ansible-playbook[Ansible Playbook]
+
 [[pluggable]]
 ==== image:images/yes.png[yes] pluggable (noun)
 *Description*: "Pluggable" refers to something that is capable of being plugged in, especially in terms of (for example) software modules. "Hot-pluggable" is also widely used with respect to hardware to indicate that it can be connected and recognized without powering down the system.

supplementary_style_guide/glossary_terms_conventions/general_conventions/r.adoc

@@ -1079,6 +1079,22 @@ Use the name of the tab when you refer to it, for example, "the *Storage* tab".
 
 *See also*:
 
+[[rulebook]]
+==== image:images/yes.png[yes] rulebook (noun)
+*Description*: A _rulebook_ is a YAML file containing a list of rules, event source definitions, and hosts to run against. 
+Rulebooks are used in Event-Driven Ansible. When using the term "rulebook" without the Ansible prefix, use lowercase _r_.
+
+Examples:
+
+* Use a rulebook in Ansible.
+* Use an Ansible Rulebook.
+
+*Use it*: yes
+
+*Incorrect forms*: Rulebook
+
+*See also*: xref:ansible-rulebook[Ansible Rulebook]
+
 [[runlevel]]
 ==== image:images/yes.png[yes] runlevel (noun)
 *Description*: A _runlevel_ is a preset operating state on a UNIX system and similar operating systems. A system can be booted in to (that is, started up in to) any of several runlevels, each of which is represented by a single-digit integer. Each runlevel designates a different system configuration and allows access to a different combination of processes (that is, instances of executing programs). There are differences in the runlevels according to the operating system. Seven runlevels are supported in the standard Linux kernel.