[openssl-commits] [web] master update

[Rich Salz]

The branch master has been updated
       via  354478fa36764b68bac3c630610efa686f67fdf0 (commit)
      from  acfec1bf62a9a12a67d49e415ea2b8086e2768ec (commit)


- Log -----------------------------------------------------------------
commit 354478fa36764b68bac3c630610efa686f67fdf0
Author: Rich Salz <rsalz at akamai.com>
Date:   Thu Jun 1 15:12:20 2017 -0400

    1.0.0 --> 1.1.0 in example

-----------------------------------------------------------------------

Summary of changes:
 source/gitrepo.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/gitrepo.html b/source/gitrepo.html
index 2b9b603..c097edf 100644
--- a/source/gitrepo.html
+++ b/source/gitrepo.html
@@ -49,8 +49,8 @@ $ git checkout .
 	<p>The <em>master</em> branch, also known as the development branch,
 	contains the latest bleeding edge code. There are also several
 	<em>stable</em> branches where stable releases come from. These take
-	the form <em>OpenSSL_x_y_z-stable</em> so, for example, the 1.0.0 stable
-	branch is <em>OpenSSL_1_0_0-stable</em>. When an actual release is
+	the form <em>OpenSSL_x_y_z-stable</em> so, for example, the 1.1.0 stable
+	branch is <em>OpenSSL_1_1_0-stable</em>. When an actual release is
 	made it is tagged in the form <em>OpenSSL_x_y_zp</em> or a beta
 	<em>OpenSSL_x_y_xp-betan</em>, though you should normally just download
 	the release tarball. Tags and branches are occasionally used for other