Version 0.1.4.

[guestfs-browser.git] / HACKING

diff --git a/HACKING b/HACKING
index 0a27b77..7cd3f2d 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -1,5 +1,5 @@
-This document describes the software architecture of the Guestfs
-Browser, useful if you want to hack on it.
+This document describes the software architecture of the
+guestfs-browser, useful if you want to hack on it.
 
 About OCaml
 -----------
@@ -7,6 +7,7 @@ About OCaml
 First of all about OCaml: Read the tutorial and other resources
 available from this site:
 
+  http://caml.inria.fr/
   http://ocaml-tutorial.org/
 
 If you are using emacs, install tuareg-mode instead of using the
@@ -30,7 +31,7 @@ Threads and messages
 
 Because libvirt and libguestfs API calls are usually long-running, we
 have to use threads, making these API calls in one thread, while
-another thread keeps the display updated.  In Guestfs Browser we use
+another thread keeps the display updated.  In guestfs-browser we use
 two threads, and send messages between them.  The main thread keeps
 the display updated and runs the glib main loop.  The slave thread
 issues libvirt and libguestfs API calls serially.  There is a FIFO
@@ -64,7 +65,7 @@ Most modules alias short names for some common libvirt and libguestfs
 modules, eg:
 
   module C = Libvirt.Connect
-  module Q = Queue
+  module G = Guestfs
 
 So when you see a function such as 'C.connect_readonly', it's really
 the function 'connect_readonly' in the [nested] module