From 23a02b18042754e571496ae1b6ee90dd399a9a96 Mon Sep 17 00:00:00 2001 From: Ohaneme Kingsley <52282848+ohansck@users.noreply.github.com> Date: Wed, 7 Sep 2022 02:32:04 +0100 Subject: [PATCH] Update README.md (#283) Edited summary "What is continuous integration". Added "be" to sentence. --- 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 13c2204..3426c6f 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 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 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.