remove repetitive word

Signed-off-by: wellweek <[email protected]>

Author: wellweek

src/couch/src/couch_proc_manager.erl

@@ -235,7 +235,7 @@ handle_info(shutdown, State) ->
     {stop, shutdown, State};
 handle_info({'EXIT', Pid, {spawn_ok, Proc0, undefined = _From}}, State) ->
     % Use ets:take/2 to assert that opener existed before removing. Also assert that
-    % the pid matches and the the client was a bogus client
+    % the pid matches and the client was a bogus client
     [{Pid, #client{from = undefined}}] = ets:take(?OPENING, Pid),
     Proc = Proc0#proc{client = undefined},
     link(Proc#proc.pid),

src/couch/src/couch_users_db.erl

@@ -186,7 +186,7 @@ validate_password(ClearPassword) ->
             ok
     end.
 
-% Get the RegExp out of the tuple and combine the the error message.
+% Get the RegExp out of the tuple and combine the error message.
 % First is with a Reason string.
 get_password_regexp_and_error_msg({RegExp, Reason}) when
     is_list(RegExp) andalso is_list(Reason) andalso

src/docs/rfcs/008-map-indexes.md

@@ -154,7 +154,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 and each value row cannot exceed 64KB.
+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.
 
 ### Key ordering

src/docs/src/config/http.rst

@@ -689,7 +689,7 @@ Virtual Hosts
         couchdb.local:5984 = /example
         *.couchdb.local:5984 = /example
 
-    If your CouchDB is listening on the the default HTTP port (80), or is
+    If your CouchDB is listening on the default HTTP port (80), or is
     sitting behind a proxy, then you don't need to specify a port number in the
     ``vhost`` key.
 

src/docs/src/ddocs/views/intro.rst

@@ -55,7 +55,7 @@ documents as we walk through how views work:
         "_rev":"4A3BBEE711",
 
         "title":"Bought a Cat",
-        "body":"I went to the the pet store earlier and brought home a little kitty...",
+        "body":"I went to the pet store earlier and brought home a little kitty...",
         "date":"2009/02/17 21:13:39"
     }
 

src/docs/src/ddocs/views/joins.rst

@@ -417,7 +417,7 @@ now have the data we need to display a post with all associated comments,
 retrieved via a single ``GET`` request.
 
 You may be asking what the 0 and 1 parts of the keys are for. They're simply
-to ensure that the post document is always sorted before the the associated
+to ensure that the post document is always sorted before the associated
 comment documents. So when you get back the results from this view for a
 specific post, you'll know that the first row contains the data for the blog
 post itself, and the remaining rows contain the comment data.

src/mango/src/mango_idx_view.erl

@@ -400,7 +400,7 @@ range(_, _, LCmp, Low, HCmp, High) ->
 % check on Arg by setting LCmp == HCmp = '$eq' and Low == High == Arg.
 %
 % If 1 < N < 5 (mid), then we set High to Arg and Arg has just
-% narrowed our range. HCmp is set the the '$lt' operator that was
+% narrowed our range. HCmp is set the '$lt' operator that was
 % part of the input.
 %
 % If N == 5 (high), We just set HCmp to '$lt' since its guaranteed

src/mem3/test/eunit/mem3_reshard_api_test.erl

@@ -391,7 +391,7 @@ individual_job_start_stop({Top, {Db1, _, _}}) ->
             JobUrl = Top ++ ?JOBS ++ ?b2l(Id),
             StUrl = JobUrl ++ "/state",
 
-            % Wait for the the job to start running and intercept it in topoff1 state
+            % Wait for the job to start running and intercept it in topoff1 state
             receive
                 {JobPid, topoff1} -> ok
             end,
@@ -410,7 +410,7 @@ individual_job_start_stop({Top, {Db1, _, _}}) ->
 
             % Start the job again
             ?assertMatch({200, _}, req(put, StUrl, #{state => running})),
-            % Wait for the the job to start running and intercept it in topoff1 state
+            % Wait for the job to start running and intercept it in topoff1 state
             receive
                 {JobPid2, topoff1} -> ok
             end,
@@ -460,7 +460,7 @@ individual_job_stop_when_cluster_stopped({Top, {Db1, _, _}}) ->
             JobUrl = Top ++ ?JOBS ++ ?b2l(Id),
             StUrl = JobUrl ++ "/state",
 
-            % Wait for the the job to start running and intercept in topoff1
+            % Wait for the job to start running and intercept in topoff1
             receive
                 {JobPid, topoff1} -> ok
             end,
@@ -487,7 +487,7 @@ individual_job_stop_when_cluster_stopped({Top, {Db1, _, _}}) ->
             % It should be possible to resume job and it should complete
             ?assertMatch({200, _}, req(put, StUrl, #{state => running})),
 
-            % Wait for the the job to start running and intercept in topoff1 state
+            % Wait for the job to start running and intercept in topoff1 state
             receive
                 {JobPid2, topoff1} -> ok
             end,

src/mem3/test/eunit/mem3_reshard_changes_feed_test.erl

@@ -219,7 +219,7 @@ continuous_feed_should_work_during_split(#{db1 := Db}) ->
             % Add 5 extra docs to the db right after changes feed was stopped
             [UpdaterPid ! add || _ <- lists:seq(1, 5)],
 
-            % The the number of documents that updater had added
+            % The number of documents that updater had added
             Ref = make_ref(),
             UpdaterPid ! {get_state, {self(), Ref}},
             DocCount =

src/setup/README.md

@@ -104,7 +104,7 @@ b. as in a, but without the Fauxton bits, just POST to /_cluster_setup
 - this request will do this:
  - on the “setup coordination node”:
   - check if we have an Erlang Cookie Secret. If not, generate
-    a UUID and set the erlang cookie to to that UUID.
+    a UUID and set the erlang cookie to that UUID.
     - store the cookie in config.ini, re-set_cookie() on startup.
   - make a POST request to the node specified in the body above
     using the admin credentials in the body above: