Typos.

Signed-off-by: Konstantina Chremmou <[email protected]>

devguide/howtos/add-field.md

@@ -57,7 +57,7 @@ Adding the new field to some existing class
 -------------------------------------------
 
 ## ocaml/idl/datamodel.ml
-Add new "field" line the class in idl/datamodel.ml. The new field might require
+Add a new "field" line to the class in the file `ocaml/idl/datamodel.ml`. The new field might require
 a suitable default value. This default value is used in case the user does not
 provide a value for the field.
 
@@ -91,7 +91,7 @@ Db.*.create – and therefore, any references to these in the code need to be
 updated. In the example, the argument ~ha_enabled:false should be added to any
 call to Db.Pool.create.
 
-## ocaml/xapi/records.ml
+### ocaml/xapi/records.ml
 If you want this field to show up in the CLI (which you probably do), you will
 also need to modify the Records module, in the file
 `ocaml/xapi/records.ml`. Find the record function for the class which
@@ -146,7 +146,7 @@ automatically. It requires some extra work, however, to enable such operations
 in the CLI.
 
 The CLI has commands such as host-param-list and host-param-get. To make a new
-field accessible by these command, the file xapi/records.ml needs to
+field accessible by these commands, the file `xapi/records.ml` needs to
 be edited. For the pool.ha-enabled field, the pool_record function in this file
 contains the following (note the convention to replace underscores by hyphens
 in the CLI):

squeezed/overview.md

@@ -4,7 +4,7 @@ layout: default
 ---
 
 Squeezed is the [xapi-project](http://github.com/xapi-project) host
-memory manager (aka balloon driver driver). Squeezed uses ballooning
+memory manager (aka balloon driver). Squeezed uses ballooning
 to move memory between running VMs, to avoid wasting host memory.
 
 Principles

xenopsd/architecture.md

@@ -75,7 +75,7 @@ The RPCs are received by the Xenops_server module and decomposed into
 - build a Xen domain: this is where the kernel or hvmloader is copied in
 - launch a device model: this is where a qemu instance is started (if one is
   required)
-- hoplug a device: this involves writing the frontend and backend trees to
+- hotplug a device: this involves writing the frontend and backend trees to
   Xenstore
 - unpause a domain (recall a Xen domain is created in the paused state)