diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8c1583f2a..16bb22e22 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -37,7 +37,7 @@ The new `blt-project` directory will have a composer dependency on your local cl
 
 While Phing and the Symfony Console can both accomplish some of the same tasks, they are different tools with different intended purposes. When developing functionality for BLT we are careful to choose the right tool for the right job.
 
-Phing is intended to be build tool. It is particularly good at stringing together multiple commands and tasks into a single target which can then be executed procedurally. We use Phing when are requirements are well suited to this strength.
+Phing is intended to be a build tool. It is particularly good at stringing together multiple commands and tasks into a single target which can then be executed procedurally. We use Phing when are requirements are well suited to this strength.
 
 The commands that Phing executes can, of course, be provided by anything. Some are native linux commands, some are provided by tools like Composer and NPM, while others may be provided by the Symfony Console component.
 
diff --git a/scripts/blt/convert-to-composer.sh b/scripts/blt/convert-to-composer.sh
index 21a411b3d..57ba177b4 100755
--- a/scripts/blt/convert-to-composer.sh
+++ b/scripts/blt/convert-to-composer.sh
@@ -47,8 +47,12 @@ if [[ $REPLY =~ ^[Yy]$ ]]; then
   # Remove unneeded files.
   echo "Removing deprecated BLT files from project."
   rm -rf build blt.sh tests/phpunit/blt
-
-  # Removing old docs.
+  rm -rf scripts/blt
+  rm -rf scripts/drupal
+  rm -rf scripts/drupal-vm
+  rm -rf scripts/git-hooks
+  rm -rf scripts/release-notes
+  rm -rf scripts/tugboat
   rm readme/acsf-setup.md
   rm readme/architecture.md
   rm readme/best-practices.md