From: Raf Czlonka <rczlonka@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Correct capitalisation of IPsec
Date: Mon, 7 Jan 2019 10:57:27 +0000 [thread overview]
Message-ID: <20190107105727.GH51930@gmail.com> (raw)
Hi all,
A quick diff to correct the capitalisation of IPsec in the main Git
repository[0].
Capitalisation on the website itself[1], will also need changing.
[0] https://git.zx2c4.com/WireGuard/
[1] https://www.wireguard.com/
Regards,
Raf
diff --git a/README.md b/README.md
index 08f8827..b8301e2 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
# WireGuard — fast, modern, secure kernel VPN tunnel
#### by [Jason A. Donenfeld](mailto:Jason@zx2c4.com) of [Edge Security](https://www.edgesecurity.com/)
-WireGuard is a novel VPN that runs inside the Linux Kernel and utilizes **state-of-the-art cryptography**. It aims to be faster, simpler, leaner, and more useful than IPSec, while avoiding the massive headache. It intends to be considerably more performant than OpenVPN. WireGuard is designed as a general purpose VPN for running on embedded interfaces and super computers alike, fit for many different circumstances. It runs over UDP.
+WireGuard is a novel VPN that runs inside the Linux Kernel and utilizes **state-of-the-art cryptography**. It aims to be faster, simpler, leaner, and more useful than IPsec, while avoiding the massive headache. It intends to be considerably more performant than OpenVPN. WireGuard is designed as a general purpose VPN for running on embedded interfaces and super computers alike, fit for many different circumstances. It runs over UDP.
**More information may be found at [WireGuard.com](https://www.wireguard.com/).**
diff --git a/src/Kconfig b/src/Kconfig
index cc2ba9f..3a68884 100644
--- a/src/Kconfig
+++ b/src/Kconfig
@@ -11,7 +11,7 @@ config WIREGUARD
select KERNEL_MODE_NEON if CPU_V7
default m
help
- WireGuard is a secure, fast, and easy to use replacement for IPSec
+ WireGuard is a secure, fast, and easy to use replacement for IPsec
that uses modern cryptography and clever networking tricks. It's
designed to be fairly general purpose and abstract enough to fit most
use cases, while at the same time remaining extremely simple to
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-01-08 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 10:57 Raf Czlonka [this message]
2019-01-08 2:04 ` Correct capitalisation of IPsec Jason A. Donenfeld
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=20190107105727.GH51930@gmail.com \
--to=rczlonka@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/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;
as well as URLs for NNTP newsgroup(s).