diff --git a/Dependencies.md b/Dependencies.md
index ed6818f..42a8d00 100644
--- a/Dependencies.md
+++ b/Dependencies.md
@@ -12,7 +12,7 @@ the following directory layout:
         Nuclex.Windows.Forms/       <-- you are here
             ...
 
-        Nuclex.Support.Native/      <-- Git: nuclex-shared-dotnet/Nuclex.Support
+        Nuclex.Support/             <-- Git: nuclex-shared-dotnet/Nuclex.Support
             ...
 
         third-party/
@@ -24,13 +24,13 @@ repository (with `--recurse-submodules`).
 
 The actual, direct requirements of the code to compile are:
 
-  * Nuclex.Support
-  * nunit (optional, if unit tests are built)
-  * nmock (optional, if unit tests are built)
+  * Nuclex.Support         (project)
+  * nunit                  (NuGet package, optional, if unit tests are built)
+  * nmock                  (NuGet package, optional, if unit tests are built)
 
 
 To Use this Library as a Binary
 -------------------------------
 
-  * Nuclex.Windows.Forms.dll
-  * Nuclex.Support.dll
+  * Nuclex.Windows.Forms   (project)
+  * Nuclex.Support         (project)
diff --git a/Directory.Build.props b/Directory.Build.props
index d2af713..e0c069b 100644
--- a/Directory.Build.props
+++ b/Directory.Build.props
@@ -8,7 +8,7 @@
     into the root 'obj' directory (instead of the intermediate directory below it),
     causing one project to overwrite the other project's dependencies.
 
-    There won't be any buld warning, just suddenly one of the projects won't be able to
+    There won't be any build warning, just suddenly one of the projects won't be able to
     access its dependencies and fail to build.
 
     Why such a lackluster system was integrated at that level rather than just left to