diff --git a/LDP/howto/docbook/Beowulf-HOWTO.xml b/LDP/howto/docbook/Beowulf-HOWTO.xml
index 5ab66719..cdd2bbcb 100644
--- a/LDP/howto/docbook/Beowulf-HOWTO.xml
+++ b/LDP/howto/docbook/Beowulf-HOWTO.xml
@@ -127,7 +127,7 @@
these two links, one can be exposed to a large number of perspectives on
the Beowulf architecture, and draw his / her own conclusions.
- What’s the difference between a true Beowulf cluster and a COW
+ What's the difference between a true Beowulf cluster and a COW
[cluster of workstations]? Brahma gives a good definition:
http://www.phy.duke.edu/brahma/beowulf_book/node62.html.
@@ -174,7 +174,7 @@
So let's get "wolfing." Choose the most powerful box to be the head
node. Install Linux there and choose every package you want. The only
requirement is that you choose "Network Servers" [in Red Hat terminology]
- because you need to have NFS and ssh. That’s all you need. In my case, I
+ because you need to have NFS and ssh. That's all you need. In my case, I
was going to do development of the Beowulf application, so I added X and C
development.
@@ -346,7 +346,7 @@ chmod 755 ~/.ssh
According to the LAM user group, only the head node needs to log
on to the slave nodes; not the other way around. Therefore when we copy
- the public key files, we only copy the head node’s key file to each
+ the public key files, we only copy the head node's key file to each
slave node, and set up the agent on the head node. This is MUCH easier
than copying all authorized_keys files to all nodes. I will describe
this in more detail later.
@@ -450,7 +450,7 @@ NO firewall
Post Install Commands
After your newly installed box reboots, log on as root again,
- and…
+ and...