From: "Flammie Pirinen" <flammie@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gnupg-user.xml
Date: Tue, 8 Nov 2005 12:41:58 +0000 [thread overview]
Message-ID: <200511081242.jA8Cfx2V016192@robin.gentoo.org> (raw)
flammie 05/11/08 12:41:58
Modified: xml/htdocs/doc/en gnupg-user.xml
Log:
s/encript/encrypt/g, English spelling fix, thanks to RiverRat for reporting
NO CONTENT CHANGE
Revision Changes Path
1.30 +5 -5 xml/htdocs/doc/en/gnupg-user.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gnupg-user.xml?rev=1.30&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gnupg-user.xml?rev=1.30&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gnupg-user.xml.diff?r1=1.29&r2=1.30&cvsroot=gentoo
Index: gnupg-user.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gnupg-user.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- gnupg-user.xml 13 Oct 2005 20:15:23 -0000 1.29
+++ gnupg-user.xml 8 Nov 2005 12:41:58 -0000 1.30
@@ -1,7 +1,7 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gnupg-user.xml,v 1.29 2005/10/13 20:15:23 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gnupg-user.xml,v 1.30 2005/11/08 12:41:58 flammie Exp $ -->
<guide link = "/doc/en/gnupg-user.xml">
<title>GnuPG Gentoo user guide</title>
@@ -605,15 +605,15 @@
<body>
<p>
-95% of the time you will use GnuPG with email, signing/encripting your outgoing
-messages and reading signed/encripted messages. So it is only fair that i talk
+95% of the time you will use GnuPG with email, signing/encrypting your outgoing
+messages and reading signed/encrypted messages. So it is only fair that i talk
about that first.
</p>
<p>
-There are two ways two sign/encript a email with GnuPG, the old way and the new
+There are two ways two sign/encrypt a email with GnuPG, the old way and the new
way :). In the old way messages would appear in plain text, with no possible
-formatting and attached files would be unsigned/unencripted, here is an example
+formatting and attached files would be unsigned/unencrypted, here is an example
of a message signed the old way:
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2005-11-08 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 12:41 Flammie Pirinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-04 19:49 [gentoo-doc-cvs] cvs commit: gnupg-user.xml Jan Kundrat
2008-03-02 22:12 Jan Kundrat
2007-12-29 16:29 Sven Vermeulen
2007-12-29 12:12 Sven Vermeulen
2007-09-23 3:00 Josh Saddler
2007-07-16 3:00 Josh Saddler
2006-07-08 2:50 Lukasz Damentko
2006-05-27 14:42 Xavier Neys
2006-05-13 22:31 vapier
2006-02-26 13:40 Xavier Neys
2006-01-10 5:00 Lukasz Damentko
2006-01-09 14:03 Lukasz Damentko
2006-01-09 13:52 Lukasz Damentko
2005-11-29 21:57 Jan Kundrat
2005-10-13 20:15 Jan Kundrat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511081242.jA8Cfx2V016192@robin.gentoo.org \
--to=flammie@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox