Skip to content

Commit 656745d

Browse files
author
Dave Cuthbert
authored
DOCSP-26955 standardize on ID (#2245)
* DOCSP-26955 standardiz on ID * DOCSP-26955 standardize on ID
1 parent db30d93 commit 656745d

40 files changed

+48
-48
lines changed

source/administration/configuration.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -349,7 +349,7 @@ The :setting:`~storage.dbPath` value controls the location of the
349349
:binary:`~bin.mongod` instance's data directory. Ensure that each database
350350
has a distinct and well labeled data directory. The
351351
:setting:`~processManagement.pidFilePath` controls where :binary:`~bin.mongod` process
352-
places it's :term:`process id (PID) <PID>` file. As this tracks the specific
352+
places it's :term:`process ID (PID) <PID>` file. As this tracks the specific
353353
:binary:`~bin.mongod` file, it is crucial that file be unique and well
354354
labeled to make it easy to start and stop these processes.
355355

source/administration/monitoring.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -529,7 +529,7 @@ use the following command to view the "balancer" lock.
529529
.. versionchanged:: 3.4
530530

531531
Starting in 3.4, the primary of the CSRS config server holds the
532-
"balancer" lock, using a process id named "ConfigServer". This lock
532+
"balancer" lock, using a process ID named "ConfigServer". This lock
533533
is never released. To determine if the balancer is running, see
534534
:ref:`sharding-balancing-is-running`.
535535

source/core/csfle/features.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ In this scenario, we secure sensitive data on a medical care management
145145
system that stores patients' personal information, insurance
146146
information, and medical records for a fictional company, *MedcoMD*.
147147
None of the patient data is public, and specific data such as their
148-
social security number (SSN, a US government-issued id number), insurance
148+
social security number (SSN, a US government-issued ID number), insurance
149149
policy number, and vital sign measurements are particularly sensitive and
150150
subject to privacy compliance. It is important for the company and the patient
151151
that the data is kept private and secure.

source/core/queryable-encryption/features.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -221,7 +221,7 @@ In this scenario, we secure sensitive data on a medical care management
221221
system that stores patients' personal information, billing
222222
information, and medical records for a fictional company, *MedcoMD*.
223223
None of the patient data is public, and specific data such as their
224-
social security number (SSN, a US government-issued id number), patient ID number,
224+
social security number (SSN, a US government-issued ID number), patient ID number,
225225
billing information, and medication information are particularly sensitive and
226226
subject to privacy compliance. It is important for the company and the patient
227227
that the data is kept private and secure.

source/core/replica-set-sync.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -301,7 +301,7 @@ Multithreaded Replication
301301
~~~~~~~~~~~~~~~~~~~~~~~~~
302302

303303
MongoDB applies write operations in batches using multiple threads to
304-
improve concurrency. MongoDB groups batches by document id (:ref:`WiredTiger
304+
improve concurrency. MongoDB groups batches by document ID (:ref:`WiredTiger
305305
<storage-wiredtiger>`) and simultaneously applies each group of
306306
operations using a different thread. MongoDB always applies write
307307
operations to a given document in their original write order.

source/core/tailable-cursors.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Consider the following behaviors related to tailable cursors:
5050
- the cursor returns the document at the "end" of the collection and
5151
then the application deletes that document.
5252

53-
A *dead* cursor has an id of ``0``.
53+
A *dead* cursor has an ID of ``0``.
5454

5555
See your :driver:`driver documentation </>` for the
5656
driver-specific method to specify the tailable cursor.

source/includes/changelogs/releases/3.2.10.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ WiredTiger
5252
- :issue:`WT-2221` Document which statistics are available via a "fast" configuration vs. an "all" configuration
5353
- :issue:`WT-2233` Investigate changing when the eviction server switches to aggressive mode.
5454
- :issue:`WT-2239` Make sure LSM cursors read up to date dsk_gen, it was racing with compact
55-
- :issue:`WT-2323` Allocate a transaction id at the beginning of join cursor iteration
55+
- :issue:`WT-2323` Allocate a transaction ID at the beginning of join cursor iteration
5656
- :issue:`WT-2843` Fix a bug in recovery if there is no filesystem truncate support
5757
- :issue:`WT-2846` Several bugs related to reconfiguring eviction server at runtime
5858
- :issue:`WT-2353` Failure to create async threads as part of a wiredtiger_open call will cause a hang

source/includes/changelogs/releases/3.4.19.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Internals
6565
~~~~~~~~~
6666

6767
- :issue:`SERVER-18985` setParameter should log at level 0
68-
- :issue:`SERVER-23818` Include Evergreen task id in metadata sent to logkeeper
68+
- :issue:`SERVER-23818` Include Evergreen task ID in metadata sent to logkeeper
6969
- :issue:`SERVER-36250` Add support for optionally logging specific negotiated TLS versions
7070
- :issue:`SERVER-37120` Turn off linux-replSet-initialsync-logkeeper Build Variant for 3.4 and 3.6 branches
7171
- :issue:`SERVER-37647` Validation hook sets FCV to 3.4 no matter what version it currently is

source/includes/changelogs/releases/3.6.18.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Internals
6767
- :issue:`SERVER-43349` Incorrect serialization for $elemMatch $not $ne
6868
- :issue:`SERVER-44325` Add polyfill for certificate chain verification
6969
- :issue:`SERVER-44435` Allow x509 authorization to be selectively enabled based on the CA
70-
- :issue:`SERVER-44868` Initialsync logkeeper and logkeeper-short tests should pass snapshot id and dataset link respectively to dsi(sys-perf)
70+
- :issue:`SERVER-44868` Initialsync logkeeper and logkeeper-short tests should pass snapshot ID and dataset link respectively to dsi(sys-perf)
7171
- :issue:`SERVER-45156` SockAddr constructor should take sockaddr, not sockaddr_storage
7272
- :issue:`SERVER-45472` Ensure RoleGraph can serialize authentication restrictions to BSON
7373
- :issue:`SERVER-45766` Remove "requires" from the server yaml

source/includes/changelogs/releases/3.6.4.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Replication
2727
- :issue:`SERVER-31399` repl.apply.batches.totalMillis does not record the time spent applying batches
2828
- :issue:`SERVER-31666` catchup_takeover_one_high_priority should use initiateWithAnyNodeAsPrimary
2929
- :issue:`SERVER-31669` Increase the election timeout in case 3 of catchup.js
30-
- :issue:`SERVER-32776` Refresh rollback id cache on increment
30+
- :issue:`SERVER-32776` Refresh rollback ID cache on increment
3131
- :issue:`SERVER-33448` Relax time diff requirements in apply_batches_totalMillis.js
3232
- :issue:`SERVER-33618` Initial sync should consider applyOps a CrudOpType
3333

0 commit comments

Comments
 (0)