Gentler lead in in mxconns post.

diff --git a/posts/mxconns.mdwn b/posts/mxconns.mdwn
index ebcb987f21cf1e1c6f9daee400b6acb2f5a374b4..efbbb754b94487480b2f8e88d1ca76340eb8e369 100644 (file)
--- a/posts/mxconns.mdwn
+++ b/posts/mxconns.mdwn
@@ -3,16 +3,16 @@
 [Lionel Cons][LC]'s [mxconns][] is an X Windows monitor and proxy.
 The author suggests you use it to enhance the security of your X
 server by monitoring for connection attempts and dangerous requests
-(e.g. keylogging).
-
-I ran into it while trying to get X forwarding working with my
-[[cluster|Abax]].  Ususally if you [[SSH]] into a remote computer and
-want to run X applications, you use `ssh -Y` to forward your X
-connection to the remote host, and everything works as expected.
-However, I could not figure out how to expose the forwarded server so
-it could except connections from other nodes in the cluster.  For
-example, if a job I had running on `n1` wanted to talk to my X server
-(e.g. via [[MPE]]), it would need to connect to `n0`:
+(e.g. keylogging).  I tend to use it as a flexible proxy fo X
+forwarding with my [[cluster|Abax]].
+
+Ususally if you [[SSH]] into a remote computer and want to run X
+applications, you use `ssh -Y` to forward your X connection to the
+remote host, and everything works as expected.  However, I could not
+figure out how to expose the forwarded server so it could except
+connections from other nodes in the cluster.  For example, if a job I
+had running on `n1` wanted to talk to my X server (e.g. via [[MPE]]),
+it would need to connect to `n0`:
 
     home <--(ssh -Y)----> n0 <--(???)----> n*