From 5942a4be8211132559be76c06c111ea86b857651 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jurica=20Zuanovi=C4=87?= Date: Wed, 23 Jan 2019 02:28:05 +0100 Subject: [PATCH] Fixing spelling errors (#27813) Fixed "goes" to "goes", "sring" to "string", "continously" to "continuously" --- guide/english/agile/integration-hell/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guide/english/agile/integration-hell/index.md b/guide/english/agile/integration-hell/index.md index 298584c0c1..bc8b4fd5c6 100644 --- a/guide/english/agile/integration-hell/index.md +++ b/guide/english/agile/integration-hell/index.md @@ -1,9 +1,9 @@ --- title: Integration Hell --- -## Integration Hell -Integration Hell is a slang term for when all the members of a development team goes through the process of implementing their code at random times with no way to incorporate the different pieces of code into one seamless string of code. The development team will have to spend several hours or days testing and tweaking the code to get it all to work. +## Integration Hell +Integration Hell is a slang term for when all the members of a development team go through the process of implementing their code at random times with no way to incorporate the different pieces of code into one seamless string of code. The development team will have to spend several hours or days testing and tweaking the code to get it all to work. In practice, the longer components are developed in isolation, the more the interfaces tend to diverge from what is expected. When the components are finally integrated at the end of the project, it would take a great deal more time than allocated, often leading to deadline pressures and difficult integration. This painful integration work at the end of the project is the eponymous hell.