You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: supplementary_style_guide/glossary_terms_conventions/general_conventions/a.adoc
+25-25Lines changed: 25 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ _Specify the system architecture of your cluster, such as `x86_64` or `aarch64`.
45
45
46
46
[[acceptor]]
47
47
==== image:images/yes.png[yes] acceptor (noun)
48
-
*Description*: In RedHat 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.
49
49
50
50
*Use it*: yes
51
51
@@ -100,7 +100,7 @@ _Specify the system architecture of your cluster, such as `x86_64` or `aarch64`.
100
100
101
101
[[action]]
102
102
==== image:images/yes.png[yes] action (noun)
103
-
*Description*: In RedHat 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_.
104
104
105
105
*Use it*: yes
106
106
@@ -144,7 +144,7 @@ _Specify the system architecture of your cluster, such as `x86_64` or `aarch64`.
144
144
145
145
[[activemq]]
146
146
==== image:images/no.png[no] ActiveMQ (noun)
147
-
*Description*: In RedHat 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.
148
148
149
149
*Use it*: no
150
150
@@ -155,7 +155,7 @@ _Specify the system architecture of your cluster, such as `x86_64` or `aarch64`.
*Description*: In RedHat 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.
159
159
160
160
*Use it*: with caution
161
161
@@ -223,51 +223,51 @@ _Valid values are `amd64`._
223
223
224
224
[[jboss-amq]]
225
225
==== image:images/yes.png[yes] AMQ (noun)
226
-
*Description*: The short product name for RedHat AMQ.
226
+
*Description*: The short product name for Red{nbsp}Hat AMQ.
*Description*: In RedHat 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.
*Description*: In RedHat 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 RedHat 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.
*Description*: In RedHat 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_.
*Description*: In RedHat 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.
*Description*: The operating system installer used in Fedora, RedHat 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.
304
304
305
305
*Use it*: yes
306
306
@@ -379,7 +379,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
379
379
380
380
[[api-server]]
381
381
==== image:images/yes.png[yes] API server (noun)
382
-
*Description*: In RedHat 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.
383
383
384
384
*Use it*: yes
385
385
@@ -401,7 +401,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
401
401
402
402
[[application]]
403
403
==== image:images/yes.png[yes] application (noun)
404
-
*Description*: In RedHat 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.
405
405
406
406
*Use it*: yes
407
407
@@ -412,7 +412,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
*Description*: _Application Streams_ are multiple versions of RedHat 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.
416
416
417
417
*Use it*: yes
418
418
@@ -456,7 +456,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
*Description*: The upstream project for AMQ Broker (link:https://activemq.apache.org/artemis/[Apache ActiveMQ Artemis]). When referring to AMQ Broker, always use the "RedHat" 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.
460
460
461
461
*Use it*: with caution
462
462
@@ -489,7 +489,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
489
489
490
490
[[asset]]
491
491
==== image:images/yes.png[yes] asset (noun)
492
-
*Description*: In RedHat JBoss BRMS and RedHat 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.
493
493
494
494
*Use it*: yes
495
495
@@ -500,7 +500,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
*Description*: In RedHat OpenShift, the Assisted Installer is an installation solution that is offered on the RedHat 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.
504
504
505
505
*Use it*: yes
506
506
@@ -579,7 +579,7 @@ The term "autodetect" is in the Vale rules and should trigger a GitHub error rep
579
579
580
580
[[autolink]]
581
581
==== image:images/yes.png[yes] autolink (noun)
582
-
*Description*: In RedHat 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.
*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 RedHat 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.
0 commit comments