diff --git a/README.asciidoc b/README.asciidoc
index 4a09f742b..b1f5ea5a4 100644
--- a/README.asciidoc
+++ b/README.asciidoc
@@ -449,12 +449,12 @@ let the character overflow into neighboring cells, which is fine if the
 neighboring cell is empty, but looks terrible if it is not.
 
 Some programs, like powerline, vim with fancy gutter symbols/status-bar, etc.
-use unicode characters from the private use area to represent symbols. Often
+misuse unicode characters from the private use area to represent symbols. Often
 these symbols are square and should be rendered in two cells.  However, since
 private use area symbols all have their width set to one in the unicode
-standard, kitty renders them either smaller or truncated. The exception (as of
-kitty 0.8.1) is if these characters are followed by a space or empty cell in
-which case kitty makes use of the extra cell to render them in two cells.
+standard, kitty renders them either smaller or truncated. The exception is if
+these characters are followed by a space or empty cell in which case kitty
+makes use of the extra cell to render them in two cells.
 
 === How do I build kitty.app on macOS?
 
@@ -491,8 +491,9 @@ for why kitty does not support background color erase.
 
 == I get errors about the terminal being unknown or opening the terminal failing when SSHing into a different computer?
 
-This happens because the kitty terminfo files are not available on the server. Either install kitty on the server,
-or simply copy over the terminfo files, using:
+This happens because the kitty terminfo files are not available on the server.
+Either install kitty on the server, or simply copy over the terminfo files,
+using:
 
 ....
 ssh myserver mkdir -p \~/.terminfo
@@ -500,8 +501,9 @@ infocmp xterm-kitty | ssh myserver "cat > /tmp/kitty.terminfo"
 ssh myserver tic -x -o \~/.terminfo /tmp/kitty.terminfo
 ....
 
-Really, the correct solution for this is to convince the OpenSSH maintainers to have ssh do this
-automatically when connecting to a server.
+Really, the correct solution for this is to convince the OpenSSH maintainers to
+have ssh do this automatically when connecting to a server, so that all
+terminals work transparently.
 
 == Resources on terminal behavior