Be more precise in docs when referring to ACME and Let's Encrypt

.gitignore

@@ -4,3 +4,8 @@ docs/Makefile
 docs/_build/
 docs/conf.py
 docs/defaults.rst
+docs/includes/global.rst
+docs/_templates/page.html
+docs/_templates/.gitkeep
+docs/_static/custom.css
+docs/_static/.gitkeep

docs/acme-integration.rst

@@ -3,11 +3,12 @@
 ACME Integration
 ================
 
-The `Automated Certificate Management Environment <https://en.wikipedia.org/wiki/Automated_Certificate_Management_Environment>`_
+.. include:: includes/all.rst
+
+`Automated Certificate Management Environment (ACME) <ACME>`_
 is a protocol that allows automated certificate requests, retrieval of signed
 certificates and certificate renewal. It was designed to enable easy deployment
-of TLS/SSL certificates by the `Let's Encrypt <https://letsencrypt.org/>`_
-project.
+of TLS/SSL certificates by the `Let's Encrypt`_ project.
 
 The ``debops.pki`` Ansible role provides support for the ACME protocol which is
 used by default with the Let's Encrypt service (there is a possibility to
@@ -239,4 +240,3 @@ can have several parameters related to the ACME certificates:
 
 ``item.acme_subject``
   List of Distinguished Name entries which define the ACME certificate Subject.
-

docs/introduction.rst

@@ -1,6 +1,8 @@
 Introduction
 ============
 
+.. include:: includes/all.rst
+
 The ``debops.pki`` role provides a standardized management of the X.509
 certificates on hosts controlled by Ansible. Other Ansible roles can utilize
 the environment created by ``debops.pki`` to automatically enable TLS/SSL
@@ -10,7 +12,7 @@ Using this role, you can bootstrap a Public Key Infrastructure in your
 environment using an internal Certificate Authority, easily switch the active
 set of certificates between internal and external Certificate Authorities, or
 use the ACME protocol to automatically obtain signed certificates from CA that
-support it (currently, `Let's Encrypt <https://letsencrypt.org/>`_).
+support it (for example `Let's Encrypt`_).
 
 Installation
 ~~~~~~~~~~~~

docs/pki-realms.rst

@@ -3,6 +3,8 @@
 PKI realms structure
 ====================
 
+.. include:: includes/all.rst
+
 The concept of PKI realms is designed to provide a standardized way for various
 applications to access X.509 certificates and private keys. The management of
 the keys and certificates is moved outside of the application into a fixed
@@ -247,21 +249,20 @@ data files for different Certificate Authorities. Each CA is described in more
 detail in a separate document, here is a brief overview:
 
 :file:`acme/`
-  This is directory used by the ACME Certificate Authority (currently only the
-  `Let's Encrypt <https://www.letsencrypt.org/>`_ CA supports this protocol).
+  This directory is for certificates issued using ACME support (for example `Let's Encrypt`_).
   It will be activated and used automatically when a host has a public IP address
   and the :program:`nginx` webserver is installed and configured to support ACME
   Challenges (see the ``debops.nginx`` role for more details).
 
 :file:`external/`
   This directory is used to manage certificates signed by an external
-  Certificate Authority. To do this, you need to provide a special ``script``
+  Certificate Authority. To do this, you need to provide a special :file:`script`
   file, which will be executed with a set of environment variables. This can be
-  used to request a certificate in and external CA, like Active Directory or
-  FreeIPA, or download a signed certificate from external location.
+  used to request a certificate from an external CA, like Active Directory or
+  FreeIPA, or download a signed certificate from an external location.
 
-  An alternative is to provide already signed :file:`cert.pem` file with optional
-  :file:`intermediate.pem` and :file:`root.pem` certificates.
+  An alternative is to provide an already signed :file:`cert.pem` file and
+  optionally the :file:`intermediate.pem` and :file:`root.pem` files.
 
 :file:`internal/`
   This directory is used by the internal ``debops.pki`` Certificate Authority
@@ -492,4 +493,3 @@ available for other applications and services:
 During this process, at various stages special "hook" scripts might be run,
 which can react to events like realm creation, activation of new certificates
 and so on.
-