Skip to content

Commit 0cace4a

Browse files
committed
Removing outdated comments from restructuring
1 parent c46d374 commit 0cace4a

File tree

25 files changed

+2
-502
lines changed

25 files changed

+2
-502
lines changed

supplementary_style_guide/glossary_terms_conventions/general_conventions/a.adoc

Lines changed: 0 additions & 35 deletions
Large diffs are not rendered by default.

supplementary_style_guide/glossary_terms_conventions/general_conventions/b.adoc

Lines changed: 0 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
// OCS: Added "In Red Hat OpenShift Container Storage, a backing store..."
21
[[backing-store]]
32
==== image:images/yes.png[yes] backing store (noun)
43
*Description*: In Red Hat OpenShift Container Storage, a _backing store_ is a type of storage resource for Multicloud Object Gateway to store data, for example, from RADOS gateway (RGW), Amazon Web Services S3, Azure Blob Storage, IBM Cloud Object Storage.
@@ -21,7 +20,6 @@
2120

2221
*See also*:
2322

24-
// BxMS: Added "In Red Hat JBoss BRMS and Red Hat JBoss BPM Suite"
2523
[[backward-chaining]]
2624
==== image:images/yes.png[yes] backward chaining (verb)
2725
*Description*: In Red Hat JBoss BRMS and Red Hat JBoss BPM Suite, _backward chaining_ is a feature of the rule engine. The backward chaining process is often referred to as derivation queries. It is not as common compared to reactive systems because Red Hat JBoss BRMS is primarily reactive forward chaining, that is, it responds to changes in your data. The backward chaining added to the rule engine is for product-like derivations.
@@ -66,7 +64,6 @@
6664

6765
*See also*: xref:bare-metal-n[bare metal (noun)]
6866

69-
// RHDS: General; kept as is
7067
[[base-dn]]
7168
==== image:images/yes.png[yes] base DN (noun)
7269
*Description*: In an LDAP directory, the _base distinguished name (DN)_ defines the starting point for operations, such as searches.
@@ -113,7 +110,6 @@ Write "Basic HTTP authentication" on first use and "Basic authentication" after
113110

114111
*See also*:
115112

116-
// EAP: Added "In Red Hat JBoss Enterprise Application Platform,"
117113
[[batch-jberet]]
118114
==== image:images/yes.png[yes] batch-jberet subsystem (noun)
119115
*Description*: In Red Hat JBoss Enterprise Application Platform, the _batch-jberet subsystem_ is used to configure and manage batch jobs. In general text, write in lowercase as two words separated by a hyphen. Write "Batch subsystem" when referring to the `batch-jberet` subsystem in titles and headings.
@@ -125,7 +121,6 @@ Write "Basic HTTP authentication" on first use and "Basic authentication" after
125121

126122
*See also*:
127123

128-
// EAP: Added "In Red Hat JBoss Enterprise Application Platform,"
129124
[[bean-validation]]
130125
==== image:images/yes.png[yes] bean-validation subsystem (noun)
131126
*Description*: In Red Hat JBoss Enterprise Application Platform, the _bean-validation subsystem_ is used to configure validation of Java bean object data. In general text, write in lowercase as two words separated by a hyphen. Write "Bean Validation subsystem" when referring to the `bean-validation` subsystem in titles and headings.
@@ -183,7 +178,6 @@ The practice of having both modes together is often referred to as _hybrid_, _ag
183178

184179
*See also*:
185180

186-
// RHDS: General; kept as is
187181
[[bind-dn]]
188182
==== image:images/yes.png[yes] bind DN (noun)
189183
*Description*: A _distinguished name (DN)_ defines the unique location of an entry in the LDAP directory. You can use the DN of an entry to bind (authenticate) to an LDAP directory. The bind DN is similar to a user name in other systems.
@@ -219,7 +213,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
219213

220214
*See also*:
221215

222-
// RHEL: Added "In Red Hat Enterprise Linux,"
223216
[[blueprint]]
224217
==== image:images/yes.png[yes] blueprint (noun)
225218
*Description*: In Red Hat Enterprise Linux, _blueprints_ are simple text files in Tom's Obvious Minimal Language (TOML) format that describe which packages, and what versions, to install into the image. They can also define a limited set of customizations that can be used to build the final image.
@@ -231,7 +224,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
231224

232225
*See also*:
233226

234-
// Ceph: Added "In Red Hat Ceph Storage,"
235227
[[bluestore]]
236228
==== image:images/yes.png[yes] BlueStore (noun)
237229
*Description*: In Red Hat Ceph Storage, _BlueStore_ is an OSD back end that uses block devices directly.
@@ -342,7 +334,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
342334

343335
*See also*: xref:broadcast-n[broadcast (noun)]
344336

345-
// AMQ: General; kept as is
346337
[[broker-cluster]]
347338
==== image:images/yes.png[yes] broker cluster (noun)
348339
*Description*: A group of brokers to be grouped together in order to share message processing load. In JBoss A-MQ 6, this was called a _network of brokers_.
@@ -354,7 +345,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
354345

355346
*See also*:
356347

357-
// AMQ: Added "In Red Hat AMQ, broker distribution is"
358348
[[broker-distribution]]
359349
==== image:images/yes.png[yes] broker distribution (noun)
360350
*Description*: In Red Hat AMQ, _broker distribution_ is the platform-independent AMQ Broker archive containing the product binaries and libraries.
@@ -366,7 +356,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
366356

367357
*See also*: xref:amq-broker[AMQ Broker], xref:broker-instance[broker instance]
368358

369-
// AMQ: Added "In Red Hat AMQ, a broker instance is"
370359
[[broker-instance]]
371360
==== image:images/yes.png[yes] broker instance (noun)
372361
*Description*: In Red Hat AMQ, a _broker instance_ is a configurable instance of AMQ Broker. Each broker instance is a separate directory containing its own runtime and configuration data. Use this term to refer to the instance, not the product.
@@ -378,7 +367,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
378367

379368
*See also*: xref:amq-broker[AMQ Broker], xref:broker-distribution[broker distribution]
380369

381-
// AMQ: General; kept as is
382370
[[brokered-messaging]]
383371
==== image:images/yes.png[yes] brokered messaging (noun)
384372
*Description*: Any messaging configuration that uses a message broker to deliver messages to destinations. _Brokered messaging_ can include brokers only, or a combination of brokers and routers.
@@ -401,7 +389,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
401389

402390
*See also*:
403391

404-
// Ceph: General; kept as is
405392
[[bucket]]
406393
==== image:images/yes.png[yes] bucket (noun)
407394
*Description*: 1) A _bucket_ in the S3 API contains objects. A bucket also defines access control lists (ACLs). Unlike folders or directories, buckets cannot contain other buckets. A bucket in the S3 API is synonymous with a _container_ in the Swift API. 2) The term "bucket" is also sometimes used in the context of a _CRUSH hierarchy_, but CRUSH buckets and S3 buckets are mutually exclusive concepts.
@@ -413,7 +400,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
413400

414401
*See also*: xref:container[container]
415402

416-
// Ceph: General; kept as is
417403
[[bucket-index]]
418404
==== image:images/yes.png[yes] bucket index (noun)
419405
*Description*: A _bucket index_ in the S3 API contains an index of objects within the bucket. The bucket index enables listing the bucket's contents.
@@ -425,7 +411,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
425411

426412
*See also*:
427413

428-
// Ceph: General; kept as is
429414
[[bucket-sharding]]
430415
==== image:images/yes.png[yes] bucket sharding (noun)
431416
*Description*: _Bucket sharding_ is a process of breaking down a bucket index into smaller more manageable shards. Bucket sharding improves performance.
@@ -448,7 +433,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
448433

449434
*See also*:
450435

451-
// OCP: General; kept as is
452436
[[build]]
453437
==== image:images/yes.png[yes] build (noun)
454438
*Description*: The process of transforming input parameters into a resulting object. Most often, the process is used to transform input parameters or source code into a runnable image.
@@ -460,7 +444,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
460444

461445
*See also*:
462446

463-
// OCP: Added "In Red Hat OpenShift,"
464447
[[build-configuration]]
465448
==== image:images/yes.png[yes] build config (noun)
466449
*Description*: In Red Hat OpenShift, a _build config_ describes a single build definition and a set of triggers for when a new build should be created. The API object for a build config is `BuildConfig`.
@@ -483,7 +466,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
483466

484467
*See also*:
485468

486-
// EAP: Added "In Red Hat JBoss Enterprise Application Platform," and removed "in JBoss EAP" later
487469
[[built-in-messaging]]
488470
==== image:images/yes.png[yes] built-in messaging (noun)
489471
*Description*: In Red Hat JBoss Enterprise Application Platform, _built-in messaging_ is an acceptable term for referring to the built-in messaging system. Capitalize "built-in" only at the beginning of a sentence. Other acceptable terms are "JBoss EAP messaging" and "JBoss EAP built-in messaging".
@@ -495,7 +477,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
495477

496478
*See also*: xref:jboss-eap-built-in-messaging[JBoss EAP built-in messaging], xref:jboss-eap-messaging[JBoss EAP messaging]
497479

498-
// BxMS: Added "In Red Hat JBoss BRMS and Red Hat JBoss BPM Suite," and removed from later in the sentence
499480
[[business-central]]
500481
==== image:images/yes.png[yes] Business Central (noun)
501482
*Description*: In Red Hat JBoss BRMS and Red Hat JBoss BPM Suite, the _Business Central_ is a web-based user interface. It is the user interface for the business rules manager and has been combined with the core Drools engine and other tools. It enables a business user to manage rules in a multi-user environment and implement changes in a controlled fashion.
@@ -507,7 +488,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
507488

508489
*See also*:
509490

510-
// BxMS: General; kept as is
511491
[[business-process]]
512492
==== image:images/yes.png[yes] business process (noun)
513493
*Description*: A _business process_ is a collection of related, structured tasks that results in achieving a specific target. It is presented as as a flowchart comprising a sequence steps necessary to achieve business goals.
@@ -519,7 +499,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
519499

520500
*See also*:
521501

522-
// BxMS: Added "In Red Hat JBoss BRMS and Red Hat JBoss BPM Suite,"
523502
[[business-resource-planner]]
524503
==== image:images/yes.png[yes] Business Resource Planner (noun)
525504
*Description*: In Red Hat JBoss BRMS and Red Hat JBoss BPM Suite, the _Business Resource Planner_ is a lightweight, embeddable, planning engine that optimizes planning problems. It helps Java TM programmers solve planning problems efficiently, and it combines optimization heuristics and metaheuristics with very efficient score calculations.
@@ -531,7 +510,6 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
531510

532511
*See also*:
533512

534-
// BxMS: General; kept as is
535513
[[business-rule]]
536514
==== image:images/yes.png[yes] business rule (noun)
537515
*Description*: A _business rule_ defines a particular aspect of a business that is intended to assert business structure or influence the behaviour of a business. Business rules often focus on access control issues and pertain to business calculations and policies of an organization.

0 commit comments

Comments
 (0)