Updated Branches: refs/heads/master 82d9d493c -> 377f353fc
Fix language in documentation use gender neutral pronouns when referring to an administrator. Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/f61882fe Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/f61882fe Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/f61882fe Branch: refs/heads/master Commit: f61882fe40dc45982c6970cb59748d21d77e4115 Parents: 82d9d49 Author: Igor GaliÄ <[email protected]> Authored: Mon Dec 2 12:08:56 2013 +0100 Committer: Igor GaliÄ <[email protected]> Committed: Mon Dec 2 12:08:56 2013 +0100 ---------------------------------------------------------------------- doc/arch/cache/cache-appendix.en.rst | 2 +- doc/arch/cache/tier-storage.en.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/trafficserver/blob/f61882fe/doc/arch/cache/cache-appendix.en.rst ---------------------------------------------------------------------- diff --git a/doc/arch/cache/cache-appendix.en.rst b/doc/arch/cache/cache-appendix.en.rst index 9a27d43..bb13b72 100644 --- a/doc/arch/cache/cache-appendix.en.rst +++ b/doc/arch/cache/cache-appendix.en.rst @@ -70,7 +70,7 @@ It becomes significant if multiple original URLs are mapped to the same remapped This is also an issue if a remapping is changed because it is effectively a time axis version of the previous case. If an original URL is remapped to a different server address then the setting determines if existing cached objects will be served for new requests (enabled) or not (disabled). Similarly if the original URL mapped to a particular URL is changed then cached objects from the initial original URL will be served from the updated original URL if pristine headers is disabled. -These collisions are not of themselves good or bad. An administrator needs to decide which is appropriate for his situation and set the value correspondingly. +These collisions are not of themselves good or bad. An administrator needs to decide which is appropriate for their situation and set the value correspondingly. If a greater degree of control is desired a plugin must used to invoke the API call :c:func:`TSCacheUrlSet()` to provide a specific cache key. http://git-wip-us.apache.org/repos/asf/trafficserver/blob/f61882fe/doc/arch/cache/tier-storage.en.rst ---------------------------------------------------------------------- diff --git a/doc/arch/cache/tier-storage.en.rst b/doc/arch/cache/tier-storage.en.rst index b802929..20bbfd6 100644 --- a/doc/arch/cache/tier-storage.en.rst +++ b/doc/arch/cache/tier-storage.en.rst @@ -37,7 +37,7 @@ The most common case for tiers is an ordered list of tiers, where higher tiers a (or more limited in capacity). This is not required. It might be that different tiers are differentiated by other properties (such as expected persistence). The design here is intended to handle both cases. -The design presumes that if a user has multiple tiers of storage and an ordering for those tiers, he will usually want +The design presumes that if a user has multiple tiers of storage and an ordering for those tiers, they will usually want content stored at one tier level to also be stored at every other lower level as well, so that it does not have to be copied if evicted from a higher tier.
