Historical-and-Process-Notes.md

@@ -18,6 +18,6 @@ So yes, the Drupal CMS repository contains all of the Drupal CMS recipes, but th
 
 The Drupal CMS Installer is an install profile that exposes the ability to choose recipes during the site install process. It applies those recipes, then as a final step, it uninstalls itself, removing the site from any lock-in effect and leaving it in the state that the recipes put it into. The installer itself contains absolutely no configuration and installs nothing beyond the stuff that it needs to do its job.
 
-The recipes that are part of Drupal CMS should, in theory, apply against _any_ install profile (although that won't necessarily always be the case - but ideally all Drupal CMS recipes would apply cleanly against Standard and Minimal, but we don't yet enforce or test this).
+The recipes that are part of Drupal CMS should, in theory, apply against _any_ install profile (although that won't necessarily always be the case; ideally all Drupal CMS recipes would apply cleanly against Standard and Minimal, but we don't yet enforce or test that).
 
 The installer should be considered part of the overall infrastructure of Drupal CMS, and track leads should generally ignore it.
\ No newline at end of file