From 9a789fc38de28fa4533c523e2ed38ba33893be2b Mon Sep 17 00:00:00 2001 From: Mark Spiezio <34728345+mark-spiezio@users.noreply.github.com> Date: Sun, 23 Feb 2020 13:09:23 -0500 Subject: [PATCH] Minor Documentation Clarifications (#3199) Clarify PEM acronym. The "public key" goes to the .crt file, not "public pair". --- tutorials/networking/ssl_certificates.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tutorials/networking/ssl_certificates.rst b/tutorials/networking/ssl_certificates.rst index 4da750814..5af20e08f 100644 --- a/tutorials/networking/ssl_certificates.rst +++ b/tutorials/networking/ssl_certificates.rst @@ -19,7 +19,7 @@ specified in the project settings: .. image:: img/ssl_certs.png This file should contain any number of public certificates in -https://en.wikipedia.org/wiki/Privacy-enhanced_Electronic_Mail format. +`PEM format `__. Of course, remember to add .crt as filter so the exporter recognizes this when exporting your project. @@ -32,8 +32,8 @@ Approach 1: self signed cert ---------------------------- The first approach is the simplest: generate a private and public -key pair, and put the public pair in the .crt file (again, in PEM -format). The private key should go to your server. +key pair and add the public key (in PEM format) to the .crt file. +The private key should go to your server. OpenSSL has `some documentation `__ about