change alternate for obfsproxy diagram; link to new pluggable transports page (a708c80fa)

@@ -27,12 +27,12 @@
     client and the bridge, will see innocent-looking transformed
     traffic instead of the actual Tor traffic.
 
-    <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="client torrc"></a>
+    <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="obfsproxy diagram"></a>
     </p>
 
     <p>
-    obfsproxy supports multiple protocols, called pluggable
-    transports, which specify how the traffic is transformed. For
+    obfsproxy supports multiple protocols, called <a href="<page docs/pluggable-transports>">pluggable
+    transports</a>, which specify how the traffic is transformed. For
     example, there might be a HTTP transport which transforms Tor
     traffic to look like regular HTTP traffic.
     </p>


...	...	@@ -27,12 +27,12 @@
27	27	client and the bridge, will see innocent-looking transformed
28	28	traffic instead of the actual Tor traffic.
29	29
30		- <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="client torrc"></a>
	30	+ <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="obfsproxy diagram"></a>
31	31	</p>
32	32
33	33	<p>
34		- obfsproxy supports multiple protocols, called pluggable
35		- transports, which specify how the traffic is transformed. For
	34	+ obfsproxy supports multiple protocols, called <a href="<page docs/pluggable-transports>">pluggable
	35	+ transports</a>, which specify how the traffic is transformed. For
36	36	example, there might be a HTTP transport which transforms Tor
37	37	traffic to look like regular HTTP traffic.
38	38	</p>
39	39

tor-webwml.git