diff --git a/src/en/clean-copy/02-Section I. The API Design/02.md b/src/en/clean-copy/02-Section I. The API Design/02.md
index 39471e7..18e0cc0 100644
--- a/src/en/clean-copy/02-Section I. The API Design/02.md	
+++ b/src/en/clean-copy/02-Section I. The API Design/02.md	
@@ -32,7 +32,7 @@ In general, there are no simple answers to those questions. Ideally, you should
 
 #### Why an API?
 
-Since our book is dedicated not to software development per se, but to developing APIs, we should look at all those questions from a different angle: why solving those problems specifically requires an API, not simply a specialized software application? In terms of our fictional example, we should ask ourselves: why provide a service to developers, allowing for brewing coffee to end users, instead of just making an app?
+Since our book is dedicated not to software development per se, but to developing APIs, we should look at all those questions from a different angle: why does solving those problems specifically require an API, not simply a specialized software application? In terms of our fictional example, we should ask ourselves: why provide a service to developers, allowing for brewing coffee to end users, instead of just making an app?
 
 In other words, there must be a solid reason to split two software development domains: there are the operators which provide APIs, and there are the operators which develop services for end users. Their interests are somehow different to such an extent, that coupling these two roles in one entity is undesirable. We will talk about the motivation to specifically provide APIs in more detail in Section III.