From f1b37a5460c04ac4a75ace2bcdf44c56fba2e05c Mon Sep 17 00:00:00 2001 From: Nate Loftsgard Date: Mon, 9 Apr 2018 12:24:04 -0500 Subject: [PATCH] Update anti-corruption-layer.md (#484) typo in word development --- docs/patterns/anti-corruption-layer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/patterns/anti-corruption-layer.md b/docs/patterns/anti-corruption-layer.md index 612f3d4f17d..5fdc8956265 100644 --- a/docs/patterns/anti-corruption-layer.md +++ b/docs/patterns/anti-corruption-layer.md @@ -17,7 +17,7 @@ Often these legacy systems suffer from quality issues such as convoluted data sc Maintaining access between new and legacy systems can force the new system to adhere to at least some of the legacy system's APIs or other semantics. When these legacy features have quality issues, supporting them "corrupts" what might otherwise be a cleanly designed modern application. -Similar issues can arise with any external system that your developmenmt team doesn't control, not just legacy systems. +Similar issues can arise with any external system that your development team doesn't control, not just legacy systems. ## Solution