From 7ee36d61f7f2d6e03aee73891ba06dd3ca70ac1b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ionic=C4=83=20Biz=C4=83u?= Date: Mon, 14 Sep 2015 09:50:23 +0300 Subject: [PATCH] doc: fix typos in README MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Fixed typo: "insallation" -> "installation" - Added an "that" in a sentence where it was needed for clarity. PR-URL: https://github.com/nodejs/node/pull/2852 Reviewed-By: Michaël Zasso Reviewed-By: Rich Trott --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fde243683ef002..b677e65d077928 100644 --- a/README.md +++ b/README.md @@ -282,7 +282,7 @@ Instructions: 1. Obtain a copy of openssl-fips-x.x.x.tar.gz. To comply with the security policy you must ensure the path through which you get the file complies with the requirements - for a "secure intallation" as described in section 6.6 in + for a "secure installation" as described in section 6.6 in the [user guide] (https://openssl.org/docs/fips/UserGuide-2.0.pdf). For evaluation/experimentation you can simply download and verify `openssl-fips-x.x.x.tar.gz` from https://www.openssl.org/source/ @@ -406,7 +406,7 @@ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273 ``` See the section above on [Verifying Binaries](#verifying-binaries) for -details on what to do with these keys to verify a downloaded file is official. +details on what to do with these keys to verify that a downloaded file is official. Previous releases of Node.js have been signed with one of the following GPG keys: