Merge pull request #14 from andreasschulze/patch-1

Update serve-stale.rst

source/topics/serve-stale.rst

@@ -8,7 +8,7 @@ Serving Stale Data
 Unbound supports serving stale data from its cache, as descibed in :RFC:`8767`.
 Serving stale data would normally break the contract between an authoritative
 name server and a caching resolver on the amount of time a record is permitted
-to be cached. Hoewver, the TTL definition of :RFC:`8767#section-4` states that:
+to be cached. However, the TTL definition of :RFC:`8767#section-4` states that:
 
     If the data is unable to be authoritatively refreshed when the TTL expires,
     the record MAY be used as though it is unexpired. 
@@ -136,4 +136,4 @@ directing your clients to places long gone.
              :term:`serve-expired-ttl-reset<serve-expired-ttl-reset: <yes or no>>`,
              :term:`serve-expired-reply-ttl<serve-expired-reply-ttl: <seconds>>` and
              :term:`serve-expired-client-timeout<serve-expired-client-timeout: <msec>>`
-             in the :doc:`/manpages/unbound.conf` manpage.
+             in the :doc:`/manpages/unbound.conf` manpage.