Skip to content

Commit a923f2b

Browse files
authored
Merge pull request #16 from Ifechukwu001/html_pages
Fix typo errors
2 parents fea796c + 2af9047 commit a923f2b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

pages/guide/ci-cd.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,9 @@ One of the core practices of DevOps is continuous integration, which has develop
2222
In [Altassians](https://www.atlassian.com/continuous-delivery/continuous-integration) words:
2323
> 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.
2424
25-
## Continuos Deployment
25+
## Continuous Deployment
2626

27-
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.
27+
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.
2828

2929
## Steps in a CI-CD Pipeline
3030

0 commit comments

Comments
 (0)