Skip to content

Commit 59446ac

Browse files
committed
Doing a sweep to add {nbsp} between 'Red' and 'Hat' throughout repo
1 parent c7e1071 commit 59446ac

File tree

31 files changed

+505
-505
lines changed

31 files changed

+505
-505
lines changed

supplementary_style_guide/glossary_terms_conventions/general_conventions/a.adoc

Lines changed: 25 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ _Specify the system architecture of your cluster, such as `x86_64` or `aarch64`.
4545

4646
[[acceptor]]
4747
==== image:images/yes.png[yes] acceptor (noun)
48-
*Description*: In Red Hat AMQ, an _acceptor_ defines the way a client can connect to a broker instance.
48+
*Description*: In Red{nbsp}Hat AMQ, an _acceptor_ defines the way a client can connect to a broker instance.
4949

5050
*Use it*: yes
5151

@@ -100,7 +100,7 @@ _Specify the system architecture of your cluster, such as `x86_64` or `aarch64`.
100100

101101
[[action]]
102102
==== image:images/yes.png[yes] action (noun)
103-
*Description*: In Red Hat OpenShift, an authorization _action_ consists of _project_, _verb_, and _resource_.
103+
*Description*: In Red{nbsp}Hat OpenShift, an authorization _action_ consists of _project_, _verb_, and _resource_.
104104

105105
*Use it*: yes
106106

@@ -144,7 +144,7 @@ _Specify the system architecture of your cluster, such as `x86_64` or `aarch64`.
144144

145145
[[activemq]]
146146
==== image:images/no.png[no] ActiveMQ (noun)
147-
*Description*: In Red Hat JBoss Enterprise Application Platform, do not use "ActiveMQ" by itself to refer to the built-in messaging technology for JBoss EAP.
147+
*Description*: In Red{nbsp}Hat JBoss Enterprise Application Platform, do not use "ActiveMQ" by itself to refer to the built-in messaging technology for JBoss EAP.
148148

149149
*Use it*: no
150150

@@ -155,7 +155,7 @@ _Specify the system architecture of your cluster, such as `x86_64` or `aarch64`.
155155

156156
[[activemq-artemis]]
157157
==== image:images/caution.png[with caution] ActiveMQ Artemis (noun)
158-
*Description*: In Red Hat JBoss Enterprise Application Platform, use "ActiveMQ Artemis" only when describing the technology used to implement the built-in messaging for JBoss EAP.
158+
*Description*: In Red{nbsp}Hat JBoss Enterprise Application Platform, use "ActiveMQ Artemis" only when describing the technology used to implement the built-in messaging for JBoss EAP.
159159

160160
*Use it*: with caution
161161

@@ -223,51 +223,51 @@ _Valid values are `amd64`._
223223

224224
[[jboss-amq]]
225225
==== image:images/yes.png[yes] AMQ (noun)
226-
*Description*: The short product name for Red Hat AMQ.
226+
*Description*: The short product name for Red{nbsp}Hat AMQ.
227227

228228
*Use it*: yes
229229

230230
[.vale-ignore]
231-
*Incorrect forms*: A-MQ, JBoss AMQ, Red Hat A-MQ, Red Hat AMQ
231+
*Incorrect forms*: A-MQ, JBoss AMQ, Red{nbsp}Hat A-MQ, Red{nbsp}Hat AMQ
232232

233-
*See also*: xref:red-hat-amq[Red Hat AMQ]
233+
*See also*: xref:red-hat-amq[Red{nbsp}Hat AMQ]
234234

235235
[[amq-broker]]
236236
==== image:images/yes.png[yes] AMQ Broker (noun)
237-
*Description*: In Red Hat AMQ, _AMQ Broker_ is a full-featured, message-oriented middleware broker. It offers specialized queueing behaviors, message persistence, and manageability.
237+
*Description*: In Red{nbsp}Hat AMQ, _AMQ Broker_ is a full-featured, message-oriented middleware broker. It offers specialized queueing behaviors, message persistence, and manageability.
238238

239239
*Use it*: yes
240240

241241
[.vale-ignore]
242-
*Incorrect forms*: A-MQ Broker, The AMQ Broker, Red Hat Broker, JBoss Broker
242+
*Incorrect forms*: A-MQ Broker, The AMQ Broker, Red{nbsp}Hat Broker, JBoss Broker
243243

244244
*See also*: xref:broker-distribution[broker distribution], xref:broker-instance[broker instance]
245245

246246
[[amq-clients]]
247247
==== image:images/yes.png[yes] AMQ Clients (noun)
248-
*Description*: In Red Hat AMQ, _AMQ Clients_ is a suite of messaging libraries supporting multiple languages and platforms. It enables users to write messaging applications that send and receive messages. AMQ Clients is a component of Red Hat AMQ.
248+
*Description*: In Red{nbsp}Hat AMQ, _AMQ Clients_ is a suite of messaging libraries supporting multiple languages and platforms. It enables users to write messaging applications that send and receive messages. AMQ Clients is a component of Red{nbsp}Hat AMQ.
249249

250250
*Use it*: yes
251251

252252
[.vale-ignore]
253-
*Incorrect forms*: A-MQ Clients, Red Hat Clients, JBoss Clients
253+
*Incorrect forms*: A-MQ Clients, Red{nbsp}Hat Clients, JBoss Clients
254254

255255
*See also*: xref:client-application[client application], xref:messaging-api[messaging API]
256256

257257
[[amq-console]]
258258
==== image:images/yes.png[yes] AMQ Console (noun)
259-
*Description*: In Red Hat AMQ, the _AMQ Console_ is a management tool for administering AMQ brokers and routers in a single graphical interface.
259+
*Description*: In Red{nbsp}Hat AMQ, the _AMQ Console_ is a management tool for administering AMQ brokers and routers in a single graphical interface.
260260

261261
*Use it*: yes
262262

263263
[.vale-ignore]
264-
*Incorrect forms*: A-MQ Console, Red Hat Console, JBoss Console
264+
*Incorrect forms*: A-MQ Console, Red{nbsp}Hat Console, JBoss Console
265265

266266
*See also*:
267267

268268
[[amq-core-protocol-jms]]
269269
==== image:images/yes.png[yes] AMQ Core Protocol JMS (noun)
270-
*Description*: In Red Hat AMQ, the _AMQ Core Protocol JMS_ is an implementation of the Java Message Service (JMS) using the ActiveMQ Artemis Core protocol. This is sometimes called _Core JMS_.
270+
*Description*: In Red{nbsp}Hat AMQ, the _AMQ Core Protocol JMS_ is an implementation of the Java Message Service (JMS) using the ActiveMQ Artemis Core protocol. This is sometimes called _Core JMS_.
271271

272272
*Use it*: yes
273273

@@ -278,12 +278,12 @@ _Valid values are `amd64`._
278278

279279
[[amq-interconnect]]
280280
==== image:images/yes.png[yes] AMQ Interconnect (noun)
281-
*Description*: In Red Hat AMQ, it is a messaging router that provides flexible routing of messages between any AMQP-enabled endpoints, whether they are clients, servers, brokers, or any other entity that can send or receive standard AMQP messages.
281+
*Description*: In Red{nbsp}Hat AMQ, it is a messaging router that provides flexible routing of messages between any AMQP-enabled endpoints, whether they are clients, servers, brokers, or any other entity that can send or receive standard AMQP messages.
282282

283283
*Use it*: yes
284284

285285
[.vale-ignore]
286-
*Incorrect forms*: Interconnect, Router, A-MQ Interconnect, Red Hat Interconnect, JBoss Interconnect
286+
*Incorrect forms*: Interconnect, Router, A-MQ Interconnect, Red{nbsp}Hat Interconnect, JBoss Interconnect
287287

288288
*See also*: xref:router[router]
289289

@@ -300,7 +300,7 @@ _Valid values are `amd64`._
300300

301301
[[anaconda]]
302302
==== image:images/yes.png[yes] Anaconda (noun)
303-
*Description*: The operating system installer used in Fedora, Red Hat Enterprise Linux, and their derivatives. _Anaconda_ is a set of Python modules and scripts with additional files like Gtk widgets (written in C), `systemd` units, and `dracut` libraries. Together, they form a tool that you can use to set parameters for your target operating system.
303+
*Description*: The operating system installer used in Fedora, Red{nbsp}Hat Enterprise Linux, and their derivatives. _Anaconda_ is a set of Python modules and scripts with additional files like Gtk widgets (written in C), `systemd` units, and `dracut` libraries. Together, they form a tool that you can use to set parameters for your target operating system.
304304

305305
*Use it*: yes
306306

@@ -379,7 +379,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
379379

380380
[[api-server]]
381381
==== image:images/yes.png[yes] API server (noun)
382-
*Description*: In Red Hat OpenShift, the _API server_ is a REST API endpoint for interacting with the system. New deployments and configurations can be created with this endpoint, and the state of the system can be interrogated through this endpoint as well.
382+
*Description*: In Red{nbsp}Hat OpenShift, the _API server_ is a REST API endpoint for interacting with the system. New deployments and configurations can be created with this endpoint, and the state of the system can be interrogated through this endpoint as well.
383383

384384
*Use it*: yes
385385

@@ -401,7 +401,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
401401

402402
[[application]]
403403
==== image:images/yes.png[yes] application (noun)
404-
*Description*: In Red Hat OpenShift, although the term _application_ is not a specific API object type, customers still create and host applications, and using the term within certain contexts is acceptable. For example, the term _application_ might refer to some combination of an image, a Git repository, or a replication controller, and this application might be running PHP, MySQL, Ruby, JBoss, or something else.
404+
*Description*: In Red{nbsp}Hat OpenShift, although the term _application_ is not a specific API object type, customers still create and host applications, and using the term within certain contexts is acceptable. For example, the term _application_ might refer to some combination of an image, a Git repository, or a replication controller, and this application might be running PHP, MySQL, Ruby, JBoss, or something else.
405405

406406
*Use it*: yes
407407

@@ -412,7 +412,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
412412

413413
[[application-stream]]
414414
==== image:images/yes.png[yes] Application Stream (noun)
415-
*Description*: _Application Streams_ are multiple versions of Red Hat Enterprise Linux user-space components that are delivered and updated more frequently than the core operating system packages. Application Streams can be packaged as RPM packages, modules, or Software Collections. Do not confuse Application Streams with "AppStream", the repository through which Application Streams and other components are distributed.
415+
*Description*: _Application Streams_ are multiple versions of Red{nbsp}Hat Enterprise Linux user-space components that are delivered and updated more frequently than the core operating system packages. Application Streams can be packaged as RPM packages, modules, or Software Collections. Do not confuse Application Streams with "AppStream", the repository through which Application Streams and other components are distributed.
416416

417417
*Use it*: yes
418418

@@ -456,7 +456,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
456456

457457
[[artemis]]
458458
==== image:images/caution.png[with caution] Artemis (noun)
459-
*Description*: The upstream project for AMQ Broker (link:https://activemq.apache.org/artemis/[Apache ActiveMQ Artemis]). When referring to AMQ Broker, always use the "Red Hat" product name.
459+
*Description*: The upstream project for AMQ Broker (link:https://activemq.apache.org/artemis/[Apache ActiveMQ Artemis]). When referring to AMQ Broker, always use the "Red{nbsp}Hat" product name.
460460

461461
*Use it*: with caution
462462

@@ -489,7 +489,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
489489

490490
[[asset]]
491491
==== image:images/yes.png[yes] asset (noun)
492-
*Description*: In Red Hat JBoss BRMS and Red Hat JBoss BPM Suite, an _asset_ is anything that can be stored as a version in the artifact repository. Assets can be business rules, packages, business processes, decision tables, fact models, or domain-specific language (DSL) files.
492+
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, an _asset_ is anything that can be stored as a version in the artifact repository. Assets can be business rules, packages, business processes, decision tables, fact models, or domain-specific language (DSL) files.
493493

494494
*Use it*: yes
495495

@@ -500,7 +500,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
500500

501501
[[assisted-installer]]
502502
==== image:images/yes.png[yes] Assisted Installer (noun)
503-
*Description*: In Red Hat OpenShift, the Assisted Installer is an installation solution that is offered on the Red Hat Hybrid Cloud Console to provide Software-as-a-Service functionality for cluster installations.
503+
*Description*: In Red{nbsp}Hat OpenShift, the Assisted Installer is an installation solution that is offered on the Red{nbsp}Hat Hybrid Cloud Console to provide Software-as-a-Service functionality for cluster installations.
504504

505505
*Use it*: yes
506506

@@ -579,7 +579,7 @@ The term "autodetect" is in the Vale rules and should trigger a GitHub error rep
579579

580580
[[autolink]]
581581
==== image:images/yes.png[yes] autolink (noun)
582-
*Description*: In Red Hat AMQ, _autolink_ is an AMQ Interconnect configurable entity that defines a link between the router and a queue, topic, or service in an external broker.
582+
*Description*: In Red{nbsp}Hat AMQ, _autolink_ is an AMQ Interconnect configurable entity that defines a link between the router and a queue, topic, or service in an external broker.
583583

584584
*Use it*: yes
585585

@@ -656,7 +656,7 @@ _Valid values are `arm64`._
656656

657657
[[arm]]
658658
==== image:images/yes.png[yes] Azure Resource Manager (noun)
659-
*Description*: In Microsoft Azure, the _Azure Resource Manager (ARM)_ is a management mode that deploys, manages, and monitors resources in the Microsoft Azure portal. ARM mode is the default for Azure CLI 2.0. Microsoft Azure resources can be managed remotely from a Red Hat Enterprise Linux server. ARM replaces Azure Service Management (ASM) as the preferred mode for managing resources in Microsoft Azure.
659+
*Description*: In Microsoft Azure, the _Azure Resource Manager (ARM)_ is a management mode that deploys, manages, and monitors resources in the Microsoft Azure portal. ARM mode is the default for Azure CLI 2.0. Microsoft Azure resources can be managed remotely from a Red{nbsp}Hat Enterprise Linux server. ARM replaces Azure Service Management (ASM) as the preferred mode for managing resources in Microsoft Azure.
660660

661661
*Use it*: yes
662662

0 commit comments

Comments
 (0)