From 2af90479dd8cb0452e51837d647efd9d5027d6a4 Mon Sep 17 00:00:00 2001 From: "Ifechukwu T. Ogidi" <ogidiifechukwu6@gmail.com> Date: Sat, 9 Mar 2024 16:46:06 +0100 Subject: [PATCH] Fix typo errors --- pages/guide/ci-cd.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/guide/ci-cd.mdx b/pages/guide/ci-cd.mdx index 165cc7c..fd75c11 100644 --- a/pages/guide/ci-cd.mdx +++ b/pages/guide/ci-cd.mdx @@ -22,9 +22,9 @@ One of the core practices of DevOps is continuous integration, which has develop In [Altassians](https://www.atlassian.com/continuous-delivery/continuous-integration) words: > Continuous integration (CI) is the practice of automating the integration of code changes from multiple contributors into a single software project. It’s a primary DevOps best practice, allowing developers to frequently merge code changes into a central repository where builds and tests then run. Automated tools are used to assert the new code’s correctness before integration. -## Continuos Deployment +## Continuous Deployment -Continuous Deployment refers to code that, when integrated/merged, is deployed automatically to the productions environment of the app. There's no human intervention, amd only a failed test will prevent a new change/feature to be deployed to production. The reason this and Continuous Delivery are often both included in CD is because typical CI/CD pipelines will include both, and they both compliment each other. +Continuous Deployment refers to code that, when integrated/merged, is deployed automatically to the productions environment of the app. There's no human intervention, and only a failed test will prevent a new change/feature to be deployed to production. The reason this and Continuous Delivery are often both included in CD is because typical CI/CD pipelines will include both, and they both compliment each other. ## Steps in a CI-CD Pipeline