diff --git a/hudsonbook-content/src/main/resources/ch04.xml b/hudsonbook-content/src/main/resources/ch04.xml
index d181eac3..c89d7a20 100644
--- a/hudsonbook-content/src/main/resources/ch04.xml
+++ b/hudsonbook-content/src/main/resources/ch04.xml
@@ -252,7 +252,7 @@
     can use them directly in your build script, using the
     <literal moreinfo="none">${key}</literal> or <literal moreinfo="none">$key</literal> notation (so
     <literal moreinfo="none">${ldapserver}</literal> or <literal moreinfo="none">$ldapserver</literal> in the
-    example give above. This is the simplest approach, but means that there is
+    example given above. This is the simplest approach, but means that there is
     a tight coupling between your build job configuration and your build
     scripts.</para>
     <para>If your script uses a different property name (one containing dots,
@@ -345,7 +345,7 @@
     within your organization. This lets you provide standard installations on
     a local server and makes for faster automatic installations. When you use
     this option, Jenkins also lets you specify a label, which will restrict
-    the use of this installation to the build notes with this label. This is a
+    the use of this installation to the build nodes with this label. This is a
     useful technique if you need to install a specific version of a tool on
     certain build machines. The same approach can also be used for other build
     tools (such as Maven and Ant).</para>