35075: improve manual format

also fixed a ChangeLog entry for 35034 (2015-05-06)

1 files changed, 10 insertions, 8 deletions

diff --git a/Doc/Zsh/mod_clone.yo b/Doc/Zsh/mod_clone.yo
index a0bf42b17..02dc5be0e 100644
--- a/Doc/Zsh/mod_clone.yo
+++ b/Doc/Zsh/mod_clone.yo
@@ -20,7 +20,8 @@ and non-zero on error.
 The target of tt(clone) should be an unused terminal, such as an unused virtual
 console or a virtual terminal created by
 
-xterm -e sh -c 'trap : INT QUIT TSTP; tty; while :; do sleep 100000000; done'
+example(xterm -e sh -c 'trap : INT QUIT TSTP; tty;
+        while :; do sleep 100000000; done')
 
 Some words of explanation are warranted about this long xterm command
 line: when doing clone on a pseudo-terminal, some other session
@@ -28,14 +29,15 @@ line: when doing clone on a pseudo-terminal, some other session
 the terminal. Hence the cloned zsh cannot acquire the pseudo-terminal
 as a controlling tty. That means two things:
 
-      the job control signals will go to the sh-started-by-xterm process
-      group (that's why we disable INT QUIT and TSTP with trap; otherwise
-      the while loop could get suspended or killed)
+startitemize()
+itemiz(the job control signals will go to the sh-started-by-xterm process
+group (that's why we disable INT QUIT and TSTP with trap; otherwise
+the while loop could get suspended or killed))
+itemiz(the cloned shell will have job control disabled, and the job
+control keys (control-C, control-\ and control-Z) will not work.)
+enditemize()
 
-      the cloned shell will have job control disabled, and the job
-      control keys (control-C, control-\ and control-Z) will not work.
-
-This does not apply when cloning to an bf(unused) vc.
+This does not apply when cloning to an em(unused) vc.
 
 Cloning to a used (and unprepared) terminal will result in two
 processes reading simultaneously from the same terminal, with