docs: replace emdash characters with plain ASCII

[tahoe-lafs/tahoe-lafs.git] / docs / about.rst

diff --git a/docs/about.rst b/docs/about.rst
index 25726fc816db40bebdd3417de9e3df1cafd3f3c7..3a23a055098a01389f425199ad5fdebad9c6aff7 100644 (file)
--- a/docs/about.rst
+++ b/docs/about.rst
@@ -27,7 +27,7 @@ these service providers spend considerable effort and expense trying to
 mitigate these risks.
 
 What we mean by "security" is something different.  *The service provider
-never has the ability to read or modify your data in the first place—never.*
+never has the ability to read or modify your data in the first place: never.*
 If you use Tahoe-LAFS, then all of the threats described above are non-issues
 to you.  Not only is it easy and inexpensive for the service provider to
 maintain the security of your data, but in fact they couldn't violate its
@@ -38,11 +38,11 @@ This guarantee is integrated naturally into the Tahoe-LAFS storage system and
 doesn't require you to perform a manual pre-encryption step or cumbersome key
 management.  (After all, having to do cumbersome manual operations when
 storing or accessing your data would nullify one of the primary benefits of
-using cloud storage in the first place—convenience.)
+using cloud storage in the first place: convenience.)
 
 Here's how it works:
 
-.. image:: https://tahoe-lafs.org/~zooko/network-and-reliance-topology.png
+.. image:: network-and-reliance-topology.svg
 
 A "storage grid" is made up of a number of storage servers.  A storage server
 has direct attached storage (typically one or more hard disks).  A "gateway"