You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficcontrol.apache.org by mi...@apache.org on 2018/09/26 13:51:47 UTC

[trafficcontrol] 30/46: What's with the arrow?

This is an automated email from the ASF dual-hosted git repository.

mitchell852 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git

commit 22a2610a21fd42346183d469246784ec65d33db2
Author: ocket8888 <oc...@gmail.com>
AuthorDate: Mon Sep 17 06:17:40 2018 -0600

    What's with the arrow?
---
 docs/source/overview/traffic_ops.rst | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/docs/source/overview/traffic_ops.rst b/docs/source/overview/traffic_ops.rst
index 9b57d0c..12b01fc 100644
--- a/docs/source/overview/traffic_ops.rst
+++ b/docs/source/overview/traffic_ops.rst
@@ -13,8 +13,6 @@
 .. limitations under the License.
 ..
 
-.. |arrow| image:: fwda.png
-
 Traffic Ops
 ===========
 Traffic Ops is the tool for administration (configuration and monitoring) of all components in a Traffic Control CDN. Traffic Portal uses Traffic Ops APIs to manage servers, cache groups, delivery services, etc. In many cases, a configuration change requires propagation to several, or even all, caches and only explicitly after or before the same change propagates to Traffic Router. Traffic Ops takes care of this required consistency between the different components and their configuratio [...]
@@ -29,8 +27,8 @@ Traffic Ops is in the process of migrating from Perl to Go, and currently runs a
 
 .. _trops-ext:
 
-|arrow| Traffic Ops Extension
------------------------------
+Traffic Ops Extension
+---------------------
 Traffic Ops Extensions are a way to enhance the basic functionality of Traffic Ops in a custom manner. There are two types of extensions:
 
 Check Extension