[6.0] 9496176d8 s/belive/believe/

[Dridi Boukelmoune]

commit 9496176d8b340b7e67d288245736b0f788543f5e
Author: Dridi Boukelmoune <dridi.boukelmoune at gmail.com>
Date:   Mon Sep 17 09:41:40 2018 +0200

    s/belive/believe/
    
    Conflicts:
            doc/sphinx/whats-new/upgrading-6.1.rst

diff --git a/doc/sphinx/phk/firstdesign.rst b/doc/sphinx/phk/firstdesign.rst
index 32f27b2a2..fee1943f8 100644
--- a/doc/sphinx/phk/firstdesign.rst
+++ b/doc/sphinx/phk/firstdesign.rst
@@ -176,7 +176,7 @@ where we kept thinking in the old frame of reference (ie: Squid)::
 	to ask are:
 
 		How long time after the expiry can we serve a cached copy
-		of this document while we have reason to belive the backend
+		of this document while we have reason to believe the backend
 		can supply us with an update ?
 
 		How long time after the expiry can we serve a cached copy
diff --git a/doc/sphinx/whats-new/changes-6.0.rst b/doc/sphinx/whats-new/changes-6.0.rst
index 55001dde4..41fd5052e 100644
--- a/doc/sphinx/whats-new/changes-6.0.rst
+++ b/doc/sphinx/whats-new/changes-6.0.rst
@@ -103,7 +103,7 @@ variant symbols, presently symbols which are different in
 ``vcl 4.0`` and ``vcl 4.1``.
 
 The "prototype" information in the VMOD shared library has been
-changed to JSON, (look in your vcc_if.c file if you don't belive
+changed to JSON, (look in your vcc_if.c file if you don't believe
 me), and this can express more detailed information, presently
 the optional arguments.