diff --git a/instruction/essentials/techStack/techStack.md b/instruction/essentials/techStack/techStack.md
index e6a90dc3..5f49cf8d 100644
--- a/instruction/essentials/techStack/techStack.md
+++ b/instruction/essentials/techStack/techStack.md
@@ -6,7 +6,7 @@ Here is what our stack looks like: React for the web framework, talking to Caddy
 
 ![260 tech stack](essentialsTechStack260.jpg)
 
-The key with a tech stack is the realization that there is no one answer to the question of what technology to use where, and the answer continually evolves. Usually you will use what the company you work for has invested in. Migrating to a new stack is very expensive and error prone. So learning how to maximize your effectiveness, regardless of the technology, will make you very valuable. Being discontent because the latest new toy is not being used, will usually cause an unnecessary disruption to the team. However, if you can validate that a change in the tech stack will produce significant monetary, performance, or security gains, then you will greatly benefit your team.
+The key with a tech stack is the realization that there is no one answer to the question of what technology to use where, and the answer continually evolves. Usually you will use what the company you work for has invested in. Migrating to a new stack is very expensive and error prone. So learning how to maximize your effectiveness, regardless of the technology, will make you very valuable. Being discontent because the latest new toy is not being used will usually cause an unnecessary disruption to the team. However, if you can validate that a change in the tech stack will produce significant monetary, performance, or security gains, then you will greatly benefit your team.
 
 ## Complex technology stack