From fd2aee9dd936048736f85173a6ff3d38dbb341db Mon Sep 17 00:00:00 2001 From: Jason Cooke Date: Sun, 14 Jul 2019 22:25:59 +1200 Subject: [PATCH] docs: fix typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 43e9439..2ee948f 100644 --- a/README.md +++ b/README.md @@ -54,7 +54,7 @@ Aspect-oriented programming (AOP) is used to encapsulate "cross-cutting" concern If we implemented the above requirements using regular OOP there'd be some drawbacks: -Good OOP says a class should have a single responsibility, however adding on extra *cross-cutting* requirements means a class that is taking on other responsibilites. For example you might have a **StoreClient** that is supposed to be all about making purchases from an online store. Add in some cross-cutting requirements and it might also have to take on the roles of logging, security and recommendations. This is not great because: +Good OOP says a class should have a single responsibility, however adding on extra *cross-cutting* requirements means a class that is taking on other responsibilities. For example you might have a **StoreClient** that is supposed to be all about making purchases from an online store. Add in some cross-cutting requirements and it might also have to take on the roles of logging, security and recommendations. This is not great because: * Our StoreClient is now harder to understand and maintain. * These cross-cutting requirements are duplicated and spread throughout our app.