docs: Use consistent spelling of CircleCI.

docs/contributing/code-reviewing.md

@@ -73,7 +73,7 @@ this?". Good choices include
   in [#10618](https://github.com/zulip/zulip/pull/10618), browse to
   bottom and click the red X next to `c6044ee` to see the build jobs
   for that commit. You can see that there are 5 build jobs in total.
-  All the 5 jobs run in Circle CI. You can see what caused
+  All the 5 jobs run in CircleCI. You can see what caused
   the job to fail by clicking on the failed job. This will open
   up a page in the CI that has more details on why the job failed.
   For example [this](https://circleci.com/gh/zulip/zulip/16617)

docs/git/cloning.md

@@ -103,7 +103,7 @@ first-time contributors][zulip-rtd-dev-first-time].
 
 This step is optional, but recommended.
 
-The Zulip Server project is configured to use [Circle CI][circle-ci]
+The Zulip Server project is configured to use [CircleCI][circle-ci]
 to test and create builds upon each new commit and pull request.
 CircleCI is the primary CI that runs frontend and backend
 tests across a wide range of Ubuntu distributions.
@@ -120,13 +120,13 @@ you make changes, you use a fast edit-refresh cycle running individual
 tests locally until your changes work.  But then once you've gotten
 the tests you'd expect to be relevant to your changes working, push a
 branch to run the full test suite in CircleCI before
-you create a pull request.  While you wait for Circle CI jobs
+you create a pull request.  While you wait for CircleCI jobs
 to run, you can start working on your next task.  When the tests finish,
 you can create a pull request that you already know passes the tests.
 
 ### Setup CircleCI
 
-First, sign in to [Circle CI][circle-ci] with your GitHub account and authorize
+First, sign in to [CircleCI][circle-ci] with your GitHub account and authorize
 CircleCI to access your GitHub account and repositories. Once you've logged
 in click on **Add Projects** in right sidebar. This will list all your GitHub
 repositories. Now goto the row of Zulip and click on **Set Up Project**.

docs/git/using.md

@@ -125,8 +125,9 @@ Now you're ready to work on the issue or feature.
 
 ## Run linters and tests locally
 
-In addition to having Circle CI run tests and linters each time you push a new
-commit, you can also run them locally. See [testing](../testing/testing.md) for details.
+In addition to having CircleCI run tests and linters each time you
+push a new commit, you can also run them locally. See
+[testing](../testing/testing.md) for details.
 
 ## Stage changes
 

docs/testing/linters.md

@@ -48,8 +48,8 @@ note are:
 * `--skip` and `--only`: Only run certain linters.
 * `-m`: Only check modified files.
 
-Finally, you can rely on our Circle CI setup to run linters for you, but
-it is good practice to run lint checks locally.
+Finally, you can rely on our CircleCI setup to run linters for you,
+but it is good practice to run lint checks locally.
 
 ```eval_rst
 .. important::

tools/ci/production-install

@@ -20,7 +20,7 @@ fi
 "$ZULIP_PATH"/scripts/setup/install --self-signed-cert --hostname 127.0.0.1 --email circleci@example.com
 
 cat >>/etc/zulip/settings.py <<EOF
-# Circle CI override settings above
+# CircleCI override settings above
 AUTHENTICATION_BACKENDS = ( 'zproject.backends.EmailAuthBackend', )
 NOREPLY_EMAIL_ADDRESS = 'noreply@circleci.example.com'
 ALLOWED_HOSTS = []

tools/commit-message-lint

@@ -1,7 +1,7 @@
 #!/usr/bin/env bash
 
 # Lint all commit messages that are newer than upstream/master if running
-# locally or the commits in the push or PR if in Circle CI.
+# locally or the commits in the push or PR if in CircleCI.
 
 # The rules can be found in /.gitlint