diff --git a/ospo-book/content/en/01-chapter.md b/ospo-book/content/en/01-chapter.md
index 64aa7d44..66c77601 100644
--- a/ospo-book/content/en/01-chapter.md
+++ b/ospo-book/content/en/01-chapter.md
@@ -74,7 +74,7 @@ In the past, collaborative open source software development was primarily adopte
 
 Once an organization has assessed the level of open source used, contributed, or produced in the organization and why establishing an OSPO can help an organization manage the risks and opportunities of what open source, open works and collaboration brings, and ensure that its open source activities are effectively managed and aligned with the organization's strategic goals and objectives.
 
-While this is a book about Open Source Programs Offices (OSPOs), it is important to note that establishing an OSPO might not the starting point for open source operations. Before establishing an OSPO (and keep reading the content of the book), companies and organizations need to assess their current goals and relationship with using and collaborating to open source software projects.
+While this is a book about Open Source Programs Offices (OSPOs), it is important to note that establishing an OSPO might not be the starting point for open source operations. Before establishing an OSPO (and keep reading the content of the book), companies and organizations need to assess their current goals and relationship with using and collaborating to open source software projects.
 
 Below, people will find a checklist to assess and better understand their possible current stage and potential next steps.