Use #:keyword syntax in preference to :keyword

because that is Guile's default.

doc/ref/api-modules.texi

@@ -243,8 +243,8 @@ them to suit the current module's needs.  For example:
 @cindex binding renamer
 @lisp
 (use-modules ((ice-9 popen)
-              :select ((open-pipe . pipe-open) close-pipe)
-              :renamer (symbol-prefix-proc 'unixy:)))
+              #:select ((open-pipe . pipe-open) close-pipe)
+              #:renamer (symbol-prefix-proc 'unixy:)))
 @end lisp
 
 Here, the interface specification is more complex than before, and the

doc/ref/goops.texi

@@ -1491,17 +1491,17 @@ all generic functions sharing a common name:
 
 @lisp
 (define-module (math 2D-vectors)
-  :use-module (oop goops)
-  :export (x y ...))
+  #:use-module (oop goops)
+  #:export (x y ...))
 		  
 (define-module (math 3D-vectors)
-  :use-module (oop goops)
-  :export (x y z ...))
+  #:use-module (oop goops)
+  #:export (x y z ...))
 
 (define-module (my-module)
-  :use-module (math 2D-vectors)
-  :use-module (math 3D-vectors)
-  :duplicates merge-generics)
+  #:use-module (math 2D-vectors)
+  #:use-module (math 3D-vectors)
+  #:duplicates merge-generics)
 @end lisp
 
 The generic function @code{x} in @code{(my-module)} will now share
@@ -1532,10 +1532,10 @@ Sharing is dynamic, so that adding new methods to a descendant implies
 adding it to the ancestor.
 
 If duplicates checking is desired in the above example, the following
-form of the @code{:duplicates} option can be used instead:
+form of the @code{#:duplicates} option can be used instead:
 
 @lisp
-  :duplicates (merge-generics check)
+  #:duplicates (merge-generics check)
 @end lisp
 
 @node Generic Function Internals

doc/ref/tools.texi

@@ -364,7 +364,7 @@ of the form:
 
 @example
 (define-module (scripts PROGRAM)
-  :export (PROGRAM))
+  #:export (PROGRAM))
 @end example
 
 Feel free to export other definitions useful in the module context.