Convert to X.Org standard indentation & cleanup whitespace

Performed with util/modular/x-indent-all.sh, followed by manual fixups

Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

1 files changed, 15 insertions, 15 deletions

diff --git a/README b/README
index 73b367e..ae51c0d 100644
--- a/README
+++ b/README
@@ -35,23 +35,23 @@ on different machines:
 X11 -- the X11 window server will be running on machine "A" for Display "B".
 	("A" is a machine name; "B" is a display number).
 
-xscope -- xscope must be told where the X11 window server is 
-	(what machine and what display).  The options for xscope are 
-	-h<X11-host> and -d<display-number>.  In our example, -hA and -dB. 
-	Typically the display-number is not given. xscope will not try to 
+xscope -- xscope must be told where the X11 window server is
+	(what machine and what display).  The options for xscope are
+	-h<X11-host> and -d<display-number>.  In our example, -hA and -dB.
+	Typically the display-number is not given. xscope will not try to
 	connect to X11 until the client connects to xscope.
 
-client -- the client should connect to xscope rather than X11.  To avoid 
-	changing the code for the client, xscope listens on the same port 
-	as X11. If X11 and xscope are on different machines, this works 
-	well.  However, if X11 and xscope are on the same machine, this 
-	creates a port conflict.  To resolve this conflict, xscope can 
-	be given a different input or output port number, as necessary 
-	to avoid the port that X11 is listening to.  The client must connect 
-	to this offset port number.  The input port for xscope is set by 
-	-i<port-number>; the output port is set by -o<port-number>. The 
+client -- the client should connect to xscope rather than X11.  To avoid
+	changing the code for the client, xscope listens on the same port
+	as X11. If X11 and xscope are on different machines, this works
+	well.  However, if X11 and xscope are on the same machine, this
+	creates a port conflict.  To resolve this conflict, xscope can
+	be given a different input or output port number, as necessary
+	to avoid the port that X11 is listening to.  The client must connect
+	to this offset port number.  The input port for xscope is set by
+	-i<port-number>; the output port is set by -o<port-number>. The
 	default input port is 1; the default output port is 0. These ports
-	are offset by the X11 base (6000) and the display number. The client 
+	are offset by the X11 base (6000) and the display number. The client
 	attaches to xscope by changing its display number by the port offset.
 
 For example, with X11 running on "bagel", display 0 (the default), and
@@ -82,7 +82,7 @@ should probably be generated from the XCB xml protocol descriptions.
 
 There is some code to interpret typed commands from the keyboard.
    It would be possible to extend the a command language to create
-   artificial characters to be sent to X11 or the client as if they were 
+   artificial characters to be sent to X11 or the client as if they were
    generated  by the other, or to dynamically alter requests or replies.
 
     ------------------------------------------------------------