[2/6] trafficserver git commit: missing backtick for formatting

[ml...@apache.org]

missing backtick for formatting


Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/f0a6575b
Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/f0a6575b
Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/f0a6575b

Branch: refs/heads/master
Commit: f0a6575b736edde33a30487cf1490efa4536b7c3
Parents: 9bb9776
Author: Miles Libbey <ml...@apache.org>
Authored: Wed Mar 11 21:43:05 2015 -0700
Committer: Miles Libbey <ml...@apache.org>
Committed: Mon Jun 8 15:44:46 2015 -0700

----------------------------------------------------------------------
 doc/reference/configuration/records.config.en.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/trafficserver/blob/f0a6575b/doc/reference/configuration/records.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/configuration/records.config.en.rst b/doc/reference/configuration/records.config.en.rst
index ccced34..93b8f7b 100644
--- a/doc/reference/configuration/records.config.en.rst
+++ b/doc/reference/configuration/records.config.en.rst
@@ -1332,7 +1332,7 @@ Cache Control
 
    When enabled (``1``), Traffic Server will attempt to write (lock) the URL
    to cache. This is rarely useful (at the moment), since it'll only be able
-   to write to cache if the origin has ignored the ``Range:` header. For a use
+   to write to cache if the origin has ignored the ``Range:`` header. For a use
    case where you know the origin will respond with a full (``200``) response,
    you can turn this on to allow it to be cached.