From 03c3e900d4cc99ff1f8fc30bee6df22016050f72 Mon Sep 17 00:00:00 2001 From: Goldyvaiiii <01234567vss@gmail.com> Date: Mon, 30 Mar 2026 23:57:01 +0530 Subject: [PATCH] docs: fix typos in markdown documentation --- COMMITTERS.md | 2 +- src/couch_replicator/README.md | 2 +- src/docs/rfcs/003-fdb-seq-index.md | 2 +- src/docs/rfcs/008-map-indexes.md | 2 +- src/docs/rfcs/011-opentracing.md | 2 +- src/docs/rfcs/012-fdb-reduce.md | 2 +- src/docs/rfcs/014-pagination.md | 2 +- src/docs/rfcs/016-fdb-replicator.md | 2 +- src/mem3/README_reshard.md | 2 +- src/smoosh/operator_guide.md | 4 ++-- 10 files changed, 11 insertions(+), 11 deletions(-) diff --git a/COMMITTERS.md b/COMMITTERS.md index 3b25283e354..0c9d15ea8c6 100644 --- a/COMMITTERS.md +++ b/COMMITTERS.md @@ -3,7 +3,7 @@ Apache CouchDB COMMITTERS Committers are given a binding vote in certain project decisions, as well as write access to public project infrastructure. Committers are elected to the -project in recognition of their committment to Apache CouchDB. We mean this in +project in recognition of their commitment to Apache CouchDB. We mean this in the sense of being loyal to the project and its interests. A full list of committers elected to the project is available at: diff --git a/src/couch_replicator/README.md b/src/couch_replicator/README.md index 8a631219d2f..56409b53394 100644 --- a/src/couch_replicator/README.md +++ b/src/couch_replicator/README.md @@ -25,7 +25,7 @@ A description of each child: interface is `acquire/1` and `release/1`. The general idea is once a connection is established, it is kept around for `replicator.connection_close_interval` milliseconds in case another - replication task wants to re-use it. It is worth pointing out how linking + replication task wants to reuse it. It is worth pointing out how linking and monitoring is handled: workers are linked to the connection pool when they are created. If they crash, the connection pool will receive an 'EXIT' event and clean up after the worker. The connection pool also monitors diff --git a/src/docs/rfcs/003-fdb-seq-index.md b/src/docs/rfcs/003-fdb-seq-index.md index 9061c5ace5b..93b098df71f 100644 --- a/src/docs/rfcs/003-fdb-seq-index.md +++ b/src/docs/rfcs/003-fdb-seq-index.md @@ -46,7 +46,7 @@ database is relocated to a different FoundationDB cluster. Thus the majority of the time an Incarnation fits into a single byte, or two bytes if the database has been moved around a small number of times. -`Sequence`: the combinination of the current `Incarnation` for the database and +`Sequence`: the combination of the current `Incarnation` for the database and the `Versionstamp` of the transaction. Sequences are monotonically increasing even when a database is relocated across FoundationDB clusters. diff --git a/src/docs/rfcs/008-map-indexes.md b/src/docs/rfcs/008-map-indexes.md index 1562814ce58..27216196f96 100644 --- a/src/docs/rfcs/008-map-indexes.md +++ b/src/docs/rfcs/008-map-indexes.md @@ -155,7 +155,7 @@ If we have a design document like the following: ``` Each emit would be a new key/value row in the map index. Each key row cannot exceed 8KB and each value row cannot exceed 64KB. -If a document is emitted as a value, that document is not allowed to exceeed 64KB. +If a document is emitted as a value, that document is not allowed to exceed 64KB. ### Key ordering diff --git a/src/docs/rfcs/011-opentracing.md b/src/docs/rfcs/011-opentracing.md index 717511c9cb8..c02824fdbfb 100644 --- a/src/docs/rfcs/011-opentracing.md +++ b/src/docs/rfcs/011-opentracing.md @@ -134,7 +134,7 @@ Following headers on the response would be supported ## Conventions The conventions below are based on [conventions from opentracing](https://github.com/opentracing/specification/blob/main/semantic_conventions.md#standard-span-tags-and-log-fields). -All tags are optional since it is just a recomendation from open tracing to hint visualization and filtering tools. +All tags are optional since it is just a recommendation from open tracing to hint visualization and filtering tools. ### Span tags diff --git a/src/docs/rfcs/012-fdb-reduce.md b/src/docs/rfcs/012-fdb-reduce.md index b8b01e4a7af..8e09dd7a1c0 100644 --- a/src/docs/rfcs/012-fdb-reduce.md +++ b/src/docs/rfcs/012-fdb-reduce.md @@ -905,7 +905,7 @@ const query = async (opts) => { // smaller queries with the initial kvs added to the skiplist -// this is used to varify the accuracy of the insert and query +// this is used to verify the accuracy of the insert and query const simpleQueries = async () => { let result = {}; result = await query({group_level: 0}); diff --git a/src/docs/rfcs/014-pagination.md b/src/docs/rfcs/014-pagination.md index 1d3a48f7fab..8f91c9847a4 100644 --- a/src/docs/rfcs/014-pagination.md +++ b/src/docs/rfcs/014-pagination.md @@ -22,7 +22,7 @@ to handle. ## Abstract -The main addition is to add new bookmark based pagination scheme to all quiery +The main addition is to add new bookmark based pagination scheme to all query like endpoints. As a first step we would keep `_all_dbs`, `_dbs_info` and `_changes` out of scope for the following reasons: - _all_dbs - the endpoint returns a list instead of object as the rest of the endpoints diff --git a/src/docs/rfcs/016-fdb-replicator.md b/src/docs/rfcs/016-fdb-replicator.md index 7f9c7363d0b..39295584f59 100644 --- a/src/docs/rfcs/016-fdb-replicator.md +++ b/src/docs/rfcs/016-fdb-replicator.md @@ -298,7 +298,7 @@ updated with terminal states of `failed` and `completed`. Users should use Advantages: - * Simplicity: re-using `couch_jobs` means having a lot less code to maintain + * Simplicity: reusing `couch_jobs` means having a lot less code to maintain in `couch_replicator`. In the draft implementation there are about 3000 lines of code saved compared to the replicator application in CouchDB 3.x diff --git a/src/mem3/README_reshard.md b/src/mem3/README_reshard.md index 2373714851f..fc7900a2e1d 100644 --- a/src/mem3/README_reshard.md +++ b/src/mem3/README_reshard.md @@ -86,7 +86,7 @@ These are mostly random notes about various modules involved in resharding. Most * `mem3_reshard_job_sup` : Simple one for one supervisor which keeps track of running jobs. -* `mem3_reshard_store` : State persistence module. It knows how to save/restore `#job{}` and `#state{}` records to/from `_local` docs. It is also re-used for serializing `#job{}` into ejson by the HTTP API module. +* `mem3_reshard_store` : State persistence module. It knows how to save/restore `#job{}` and `#state{}` records to/from `_local` docs. It is also reused for serializing `#job{}` into ejson by the HTTP API module. * `mem3_reshard_validate` : Validate that source exists, target ranges don't have gaps in them, etc. diff --git a/src/smoosh/operator_guide.md b/src/smoosh/operator_guide.md index 3edfd3b1db4..4ac798f24c6 100644 --- a/src/smoosh/operator_guide.md +++ b/src/smoosh/operator_guide.md @@ -50,7 +50,7 @@ document bodies in the leaves of the revision tree of each document. It includes storage overhead, on-disk btree structure but does not include document bodies not in leaf nodes. So, for instance, after deleting a document, that document's body revision will become an intermediate revision tree node and its -size won't be relfected in the **active_bytes** ammount. +size won't be reflected in the **active_bytes** amount. * **total_bytes**: the size of the file on disk. @@ -153,7 +153,7 @@ And some standard names for ones we often have to add: _large_ means is very workload specific. Channels have certain defaults for their configuration, defined in the -[smoosh readme][srconfig]. It's only neccessary to set up how this channel +[smoosh readme][srconfig]. It's only necessary to set up how this channel differs from those defaults. Below, we just need to set the `min_size` and `concurrency` settings, and allow the `priority` to default to `ratio` along with the other defaults.