rewrite second paragraph of README

Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>

2 files changed, 17 insertions, 15 deletions

diff --git a/README.rst b/README.rst
index 7d74ce6..209ed00 100644
--- a/README.rst
+++ b/README.rst
@@ -6,14 +6,14 @@ Common Lisp.  You can use it to configure hosts as root, deploy services as
 unprivileged users, build and deploy containers, and produce disc images.
 
 Consfigurator's design gives you a great deal of flexibility about how to
-control the hosts you want to configure.  If you can run a command which will
-obtain input and output streams attached to an interactive POSIX sh running on
-the target host/in the target container, then you use much of Consfigurator's
-functionality to configure that host or container.  But if it is possible to
-get an implementation of Common Lisp started up on the host, then Configurator
-can transparently execute your deployment code over on the remote side, rather
-than exchanging information via POSIX sh.  This lets you use the full power of
-Common Lisp to deploy your configuration.
+control the hosts you want to configure.  If there is a command you can run
+which will obtain input and output streams attached to an interactive POSIX sh
+running on the target host/container, then with a little glue code, you can
+use much of Consfigurator's functionality to configure that host/container.
+But if it is possible to get an implementation of Common Lisp started up on
+the host, then Configurator can transparently execute your deployment code
+over on the remote side, rather than exchanging information via POSIX sh.
+This lets you use the full power of Common Lisp to deploy your configuration.
 
 Configurator has convenient abstractions for combining these different ways to
 execute your configuration on hosts with different ways of connecting to them.
diff --git a/debian/control b/debian/control
index 6b42ba1..bcdf065 100644
--- a/debian/control
+++ b/debian/control
@@ -33,13 +33,15 @@ Description: Lisp declarative configuration management system
  unprivileged users, build and deploy containers, and produce disc images.
  .
  Consfigurator's design gives you a great deal of flexibility about how to
- control the hosts you want to configure.  Input and output streams attached
- to an interactive POSIX sh running on the target host (or in the target
- container) is sufficient to use much of Consfigurator's functionality.  But
- if it is possible to get an implementation of Common Lisp started up on the
- host, then Configurator can transparently execute your deployment code over
- on the remote side, rather than exchanging information via POSIX sh.  This
- lets you use the full power of Common Lisp to deploy your configuration.
+ control the hosts you want to configure.  If there is a command you can run
+ which will obtain input and output streams attached to an interactive POSIX
+ sh running on the target host/container, then with a little glue code, you
+ can use much of Consfigurator's functionality to configure that
+ host/container.  But if it is possible to get an implementation of Common
+ Lisp started up on the host, then Configurator can transparently execute your
+ deployment code over on the remote side, rather than exchanging information
+ via POSIX sh.  This lets you use the full power of Common Lisp to deploy your
+ configuration.
  .
  Configurator has convenient abstractions for combining these different ways
  to execute your configuration on hosts with different ways of connecting to