diff --git a/content/contributing/how/first-time/what-is-a/ci/contents.lr b/content/contributing/how/first-time/what-is-a/ci/contents.lr
index 635c79f17c..c9acb0dd17 100644
--- a/content/contributing/how/first-time/what-is-a/ci/contents.lr
+++ b/content/contributing/how/first-time/what-is-a/ci/contents.lr
@@ -2,23 +2,24 @@ _model: page
---
title: CI
---
+summary: What is CI, or Continuous Integration
+---
body:
-Continuous integration, or CI, is a way that we can test code continuously.
-These systems will automatically listen for new Pull Requests and other events,
-and automatically run test suites, and other automatic processes.
+Continuous integration, or CI, is a way that we can test every code change that is made
+to a project. These systems automatically listen for new pull requests and other events,
+and automatically run test suites, and other automatic processes.
+
+We use GitHub's CI system: `Actions <https://github.com/features/actions>`_. Normally
+the *build status* of a project is displayed as an image on the project's README file.
+Green means the tests have been successful, and red means they have not. Clicking the
+image will show you the results of these tests.
-We use a number of different CI systems: `Travis CI <https://travis-ci.com/>`_
-and `BeeKeeper <https://beekeeper.beeware.org>`_ . Normally the *build status* of a
-project is displayed as an image on the project's README file. Green means the
-tests have been successful, and red means they have not. Clicking the image
-will show you the results of these tests.
---
gutter:
Unsure which CI environment is being used?
---------------------------------------------------------
+-------------------------------------------
-Check for the configuration file. `.travis.yml` is Travis, `beekeeper.yml` is BeeKeeper.
----
-summary: What is CI, or Continuous Integration
+Check for the configuration file. GitHub CI workflows are configured in the
+``.github/workflows`` directory.