\section{How to read this guide}
-If you are a system administrator and want to quickly update your services, jump right to section \ref{section:PracticalSettings}. However, we recommend that you take some time and read some of the background information, especially on how to choose your own cipher string in section \ref{section:CipherSuites} and then adapt the settings in section \ref{section:PracticalSettings} to your own needs.
+If you are a system administrator and want to quickly update your services, jump right to section \ref{section:PracticalSettings}. However, we recommend that you take some time and read through the background information we provide in this publication, especially on how to choose your own cipher string in section \ref{section:CipherSuites} and then adapt the settings in section \ref{section:PracticalSettings} to your own needs.
\section{Methods}
\label{section:Methods}
+For writing this guide, we chose to collect the most well researched facts about
+cryptography settings and let as many trusted specialists as possible review those settings.
+The review process is completely open and done on a public mailing list. The
+document is available (read-only) to the public Internet on a git server, GitHub (mirror)
+and open for public scrutiny. However, write permissions to the document are only
+granted to vetted people. The list of editors can be found in section \ref{section:Reviewers}.
+Every write operation to the document is logged via the ``git'' version control system
+and can thus be traced to a specific author. We do not trust an unknown git server.
-For writing this guide, we chose to collect the most well known facts about crypto-settings
-and let as many trusted specialists as possible review these settings. The
-review process is completely open and done on a public mailing list. The
-document is available (read-only) to the public Internet on a git server and
-open for public scrutiny. However, write permissions to the document are only
-granted to trusted people. The list of editors is made public. Every write
-operation to the document is logged via the ``git'' version control system and
-thus can be traced back to a specific author. We do not trust an unknown git
-server.
-
-Public peer-review and ``multiple eyes'' checking our recommendation is the best
-strategy we can imagine at the moment\footnote{\url{http://www.wired.com/opinion/2013/10/how-to-design-and-defend-against-the-perfect-backdoor/}}.
+Public peer-review and ``multiple eyes'' checking of our publication is the best
+strategy we can imagine at the present moment
+\footnote{\url{http://www.wired.com/opinion/2013/10/how-to-design-and-defend-against-the-perfect-backdoor/}}.