Use this bug to track the other typo:

I got following message when multiple kill switch exist, no space between "set" and "the number 2". 
"The Red Hat Bugzilla Rule Engine 'kill switch' is currently set2 times"

I think it should probably be plural form (i.e. "Rules Engine") as it will have more than one rule.

The only place I didn't change was the Changelog.

To keep consitent, we better also change the following places which also using "Rule Engine"

1. The inline history still show:
Rule Engine Rule: stress
and in the history of the bug, also show the "Rule Engine Rule"


2. Some docs:
/docs/en/html/rule-engine.html:  The Rule Engine page contains a list of rules in tables organized by Rule Group.  The details
./docs/en/html/api/extensions/RuleEngine/lib/RuleState.html:<p>Bugzilla::Extension::RuleEngine::RuleState represents an entry in the Rule Engine state table. If there are any rows where when_enabled is not set, the Rules Engine will not be run. It is an implementation of <a href="../../../Bugzilla/Object.html" class="podlinkpod"
./docs/en/html/Bugzilla-Guide.html:  The Rule Engine page contains a list of rules in tables organized by Rule Group.  The details
./docs/en/txt/Bugzilla-Guide.txt:   The Rule Engine page contains a list of rules in tables organized by
./docs/en/txt/Bugzilla-Guide.txt:          the Bugzilla Rule Engine to automate project workflow.
./docs/en/txt/Bugzilla-Guide.txt:          Rule Engine. This is done by adding them to the rule_engine

(In reply to Shirley Zhou from comment #4)
> 1. The inline history still show:
> Rule Engine Rule: stress
> and in the history of the bug, also show the "Rule Engine Rule"

Note that this string was set in the database when the change described in the history was made.  Changes made by the Rules Engine before you upgraded to version 4.4.5024 will therefore keep the old string.  To test the fix you need to look at a change made by the Rules Engine after you upgraded to 4.4.5024.

> 2. Some docs:
> /docs/en/html/rule-engine.html:  The Rule Engine page contains a list of
> rules in tables organized by Rule Group.  The details
> ./docs/en/html/api/extensions/RuleEngine/lib/RuleState.html:<p>Bugzilla::
> Extension::RuleEngine::RuleState represents an entry in the Rule Engine
> state table. If there are any rows where when_enabled is not set, the Rules
> Engine will not be run. It is an implementation of <a
> href="../../../Bugzilla/Object.html" class="podlinkpod"
> ./docs/en/html/Bugzilla-Guide.html:  The Rule Engine page contains a list of
> rules in tables organized by Rule Group.  The details
> ./docs/en/txt/Bugzilla-Guide.txt:   The Rule Engine page contains a list of
> rules in tables organized by
> ./docs/en/txt/Bugzilla-Guide.txt:          the Bugzilla Rule Engine to
> automate project workflow.
> ./docs/en/txt/Bugzilla-Guide.txt:          Rule Engine. This is done by
> adding them to the rule_engine

I can only find one instance of "Rule Engine" remaining in the docs. It was introduced by me in parallel with Simon's change and fixed by the attached patch.  Did you install the latest rh-bugzilla-docs RPM?

(In reply to Jason McDonald from comment #5)
> (In reply to Shirley Zhou from comment #4)
> > 1. The inline history still show:
> > Rule Engine Rule: stress
> > and in the history of the bug, also show the "Rule Engine Rule"
> 
> Note that this string was set in the database when the change described in
> the history was made.  Changes made by the Rules Engine before you upgraded
> to version 4.4.5024 will therefore keep the old string.  To test the fix you
> need to look at a change made by the Rules Engine after you upgraded to
> 4.4.5024.

That's not true. We need to update the field name in the database, and the history will magically be fixed on all entries thanks to the Red Hat Bugzilla fairies :)

I'll do a patch for this on Monday.

I see the problem now.  There were some instances where "Rule Engine" was split by a line break in the sources and thus didn't get caught by the original find and replace.

"Rule Engine" disappears, moving this bug to verified

This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.