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> -- [email protected] mailing list
