From a1465d2dac0d77d9717a6a5e387a5752fa82f3bd Mon Sep 17 00:00:00 2001 From: Stefan Date: Tue, 11 Jun 2024 07:10:44 -0400 Subject: [PATCH] Added missing words to CI/CD README.md. (#10259) --- topics/cicd/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/cicd/README.md b/topics/cicd/README.md index 0a8a02675..aa547b868 100644 --- a/topics/cicd/README.md +++ b/topics/cicd/README.md @@ -16,7 +16,7 @@ A development practice where developers integrate code into a shared repository frequently. It can range from a couple of changes every day or a week to a couple of changes in one hour in larger scales. -Each piece of code (change/patch) is verified, to make the change is safe to merge. Today, it's a common practice to test the change using an automated build that makes sure the code can be integrated. It can be one build which runs several tests in different levels (unit, functional, etc.) or several separate builds that all or some has to pass in order for the change to be merged into the repository. +Each piece of code (change/patch) is verified to make sure that the change is safe to merge. Today, it's a common practice to test the change using an automated build that makes sure the code can be integrated. It can be one build which runs several tests in different levels (unit, functional, etc.) or several separate builds that all or some has to pass in order for the change to be merged into the repository.