deploy: c4cfea6

print.html

@@ -261,8 +261,8 @@ <h3 id="project-composition--workspaces"><a class="header" href="#project-compos
 <p>Each of the subprojects defines a <code>workspace.josh</code> file, defining the mapping between the original central.git repository and the hierarchy in use inside of the project.</p>
 <p>In this setup, project1 and project2 can seemlessly depend on the latest version of library1, while only checking out the part of the central monorepo that's needed for their purpose.
 What's more, any changes to a shared module will be synced in both directions.</p>
-<p>If a developper of the library1 pushed a new update, both projects will get the new version, and the developper will be able to check if they broke any test.
-If a developper of project1 needs to update the library, the changes will be automatically shared back into central, and project2.</p>
+<p>If a developer of the library1 pushed a new update, both projects will get the new version, and the developer will be able to check if they broke any test.
+If a developer of project1 needs to update the library, the changes will be automatically shared back into central, and project2.</p>
 <h3 id="simplified-cicd"><a class="header" href="#simplified-cicd">Simplified CI/CD</a></h3>
 <p>With everything stored in one repo, CI/CD systems only need to look into one source for each particular
 deliverable.

usecases.html

@@ -202,8 +202,8 @@ <h3 id="project-composition--workspaces"><a class="header" href="#project-compos
 <p>Each of the subprojects defines a <code>workspace.josh</code> file, defining the mapping between the original central.git repository and the hierarchy in use inside of the project.</p>
 <p>In this setup, project1 and project2 can seemlessly depend on the latest version of library1, while only checking out the part of the central monorepo that's needed for their purpose.
 What's more, any changes to a shared module will be synced in both directions.</p>
-<p>If a developper of the library1 pushed a new update, both projects will get the new version, and the developper will be able to check if they broke any test.
-If a developper of project1 needs to update the library, the changes will be automatically shared back into central, and project2.</p>
+<p>If a developer of the library1 pushed a new update, both projects will get the new version, and the developer will be able to check if they broke any test.
+If a developer of project1 needs to update the library, the changes will be automatically shared back into central, and project2.</p>
 <h3 id="simplified-cicd"><a class="header" href="#simplified-cicd">Simplified CI/CD</a></h3>
 <p>With everything stored in one repo, CI/CD systems only need to look into one source for each particular
 deliverable.