From 3a115fdd97e99631755d2a85c7e19ccb7edfedd0 Mon Sep 17 00:00:00 2001 From: simon Date: Tue, 29 Mar 2005 14:24:14 +0000 Subject: [PATCH] Small markup fixes I just noticed, mostly use of literal double quotes where \q{} would be better. git-svn-id: svn://svn.tartarus.org/sgt/putty@5562 cda61777-01e9-0310-a592-d414129be87e --- doc/faq.but | 14 +++++++------- doc/feedback.but | 4 ++-- doc/licence.but | 4 ++-- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/faq.but b/doc/faq.but index ad27dcd0..83293ddd 100644 --- a/doc/faq.but +++ b/doc/faq.but @@ -839,13 +839,13 @@ default cipher differs from many other clients.) \e{OpenSSH 3.1p1:} configurations known to be broken (and symptoms): -\b SSH-2 with AES cipher (PuTTY says "Assertion failed! Expression: -(len & 15) == 0" in sshaes.c, or "Out of memory", or crashes) +\b SSH-2 with AES cipher (PuTTY says \q{Assertion failed! Expression: +(len & 15) == 0} in \cw{sshaes.c}, or \q{Out of memory}, or crashes) -\b SSH-2 with 3DES (PuTTY says "Incorrect MAC received on packet") +\b SSH-2 with 3DES (PuTTY says \q{Incorrect MAC received on packet}) -\b SSH-1 with Blowfish (PuTTY says "Incorrect CRC received on -packet") +\b SSH-1 with Blowfish (PuTTY says \q{Incorrect CRC received on +packet}) \b SSH-1 with 3DES @@ -857,8 +857,8 @@ bug 138 above, or use another cipher (e.g., 3DES) instead. and workarounds with older versions of OpenSSH, although it's not clear the underlying cause is the same. -\S{faq-ssh2key-ssh1conn}{Question} Why do I see "Couldn't load private -key from ..."? Why can PuTTYgen load my key but not PuTTY? +\S{faq-ssh2key-ssh1conn}{Question} Why do I see \q{Couldn't load +private key from ...}? Why can PuTTYgen load my key but not PuTTY? It's likely that you've generated an SSH protocol 2 key with PuTTYgen, but you're trying to use it in an SSH-1 connection. SSH-1 and SSH-2 keys diff --git a/doc/feedback.but b/doc/feedback.but index bba975f2..a724eac6 100644 --- a/doc/feedback.but +++ b/doc/feedback.but @@ -141,8 +141,8 @@ report a bug to us, it is useful if you include some general information: \b Tell us what version of PuTTY you are running. To find this out, -use the "About PuTTY" option from the System menu. Please \e{do not} -just tell us \q{I'm running the latest version}; e-mail can be +use the \q{About PuTTY} option from the System menu. Please \e{do +not} just tell us \q{I'm running the latest version}; e-mail can be delayed and it may not be obvious which version was the latest at the time you sent the message. diff --git a/doc/licence.but b/doc/licence.but index 7319ae29..d2d4470c 100644 --- a/doc/licence.but +++ b/doc/licence.but @@ -10,7 +10,7 @@ Justin Bradford, Ben Harris, Malcolm Smith, Markus Kuhn, and CORE SDI S.A. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files -(the "Software"), to deal in the Software without restriction, +(the \q{Software}), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, @@ -19,7 +19,7 @@ subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +THE SOFTWARE IS PROVIDED \q{AS IS}, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE -- 2.11.0