[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [ooni-probe/master] Fix spelling in test documentation
commit 6dea02f4de4cd32741b3f9a7404750dff7136183
Author: aagbsn <aagbsn@xxxxxxxx>
Date: Thu Dec 6 11:56:16 2012 +0000
Fix spelling in test documentation
---
docs/source/tests/dnstamper.rst | 6 +++---
docs/source/tests/http_host.rst | 10 +++++-----
docs/source/tests/http_invalid_request_line.rst | 4 ++--
docs/source/tests/http_requests.rst | 4 ++--
docs/source/tests/tcpconnect.rst | 2 +-
docs/source/tests/traceroute.rst | 2 +-
docs/source/writing_tests.rst | 8 ++++----
7 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/docs/source/tests/dnstamper.rst b/docs/source/tests/dnstamper.rst
index c4e6f17..8fdb572 100644
--- a/docs/source/tests/dnstamper.rst
+++ b/docs/source/tests/dnstamper.rst
@@ -22,8 +22,8 @@ lookup on the first A record address of both sets and check if they both
resolve to the same name.
NOTE: This test frequently results in false positives due to GeoIP-based
-load balancing on major global sites such as google, facebook, and
-youtube, etc.
+load balancing on major global sites such as Google, Facebook, and
+Youtube, etc.
How to run the test
===================
@@ -176,5 +176,5 @@ From running:
test_started: 1354187839.512434
...
-Notes: Query is the string repsentation of :class:twisted.names.dns.Query
+Notes: Query is the string representation of :class:twisted.names.dns.Query
diff --git a/docs/source/tests/http_host.rst b/docs/source/tests/http_host.rst
index febdc4a..ebe10e7 100644
--- a/docs/source/tests/http_host.rst
+++ b/docs/source/tests/http_host.rst
@@ -22,7 +22,7 @@ enumerating the sites that are being censored by it.
It places inside of the Host header field the hostname of the site that is to
be tested for censorship and then determines if the probe is behind a
transparent HTTP proxy (because the response from the backend server does not
-match) and if the site is censorsed, by checking if the page that it got back
+match) and if the site is censored, by checking if the page that it got back
matches the input block page.
*Why do content blocking?*
@@ -30,7 +30,7 @@ matches the input block page.
Q: Why should be do content blocking measurements with this test when we have
other tests that also do this?
-A: Why not? Although you are correct that tecnically the two tests are
+A: Why not? Although you are correct that technically the two tests are
equivalent even though the IP layer differs in the two tests.
Note: We may in the future remove the Content Blocking aspect of the HTTP Host
@@ -46,9 +46,9 @@ How to run the test
*backend url* is the url of the backend that will be used for checking if the
site is blocked or not.
-*content* is the content of a blockpage. When a transparent HTTP proxy is
-present we will do comparisons against this to verify if the requested site is
-blocked or not.
+*content* is the content of a page. When a transparent HTTP proxy is present we
+will do comparisons against this to verify if the requested site is blocked or
+not.
Sample report
diff --git a/docs/source/tests/http_invalid_request_line.rst b/docs/source/tests/http_invalid_request_line.rst
index 4ac223e..4a59df0 100644
--- a/docs/source/tests/http_invalid_request_line.rst
+++ b/docs/source/tests/http_invalid_request_line.rst
@@ -24,7 +24,7 @@ on the HTTP request line. We generate a series of requests that are not
valid HTTP requests.
The remote backend runs a TCP echo server. If the response from the backend
-does not match with what we have sent then we say that tampering is occuring.
+does not match with what we have sent then we say that tampering is occurring.
The idea behind this is that certain transparent HTTP proxies may not be
properly parsing the HTTP request line.
@@ -75,7 +75,7 @@ This generates a request that looks like this:
::
GET / HTTP/XxX
-This attemps to trigger bugs in the parsing of the HTTP version number, that
+This attempts to trigger bugs in the parsing of the HTTP version number, that
is usually being split on the `.`.
How to run the test
diff --git a/docs/source/tests/http_requests.rst b/docs/source/tests/http_requests.rst
index cc98882..6eb0d0a 100644
--- a/docs/source/tests/http_requests.rst
+++ b/docs/source/tests/http_requests.rst
@@ -21,8 +21,8 @@ and over Tor. It then compares the two responses to see if the response bodies o
proportion between the expected body length (the one over Tor) and the one over
the control network match.
-If the proportion between the two body lengths is <= a certain tollerance
-factor (by default set to 0.8), then we say that they do not match.
+If the proportion between the two body lengths is <= a certain tolerance factor
+(by default set to 0.8), then we say that they do not match.
The reason for doing so is that a lot of sites serve geolocalized content based
on the location from which the request originated from.
diff --git a/docs/source/tests/tcpconnect.rst b/docs/source/tests/tcpconnect.rst
index 7c7bd16..e92077d 100644
--- a/docs/source/tests/tcpconnect.rst
+++ b/docs/source/tests/tcpconnect.rst
@@ -16,7 +16,7 @@ Details
Description
===========
-This test performs TCP connections to a set of sepecified IP:PORT pairs and
+This test performs TCP connections to a set of specified IP:PORT pairs and
reports the reason for which it failed connecting to the target address.
The reason for failure may be: "timeout", when the connection timed out,
diff --git a/docs/source/tests/traceroute.rst b/docs/source/tests/traceroute.rst
index 898fc30..5b18454 100644
--- a/docs/source/tests/traceroute.rst
+++ b/docs/source/tests/traceroute.rst
@@ -40,7 +40,7 @@ other means that are not the src and destination IP address.
In particular the ICMP TTL expired citations will contain the IP headers.
-We could theorically strip these though even if that were the case there would
+We could theoretically strip these though even if that were the case there would
still be at least a reduction of the anonymity set given by the fact that we
received a TTL expired from a router in a certain network range.
diff --git a/docs/source/writing_tests.rst b/docs/source/writing_tests.rst
index f74f3f0..e4d03e4 100644
--- a/docs/source/writing_tests.rst
+++ b/docs/source/writing_tests.rst
@@ -41,7 +41,7 @@ specifies what command line option may be used to control this value.
By default the ``inputProcessor`` is set to read the file line by line and
strip newline characters. To change this behavior you must set the
-``inputProcessor`` attribute to a function that takes as arugment a file
+``inputProcessor`` attribute to a function that takes as argument a file
descriptor and yield the next item. The default ``inputProcessor`` looks like
this::
@@ -57,7 +57,7 @@ Setup and command line passing
------------------------------
Tests may define the `setUp` method that will be called every time the Test
-Case object is intantiated, in here you may place some common logic to all your
+Case object is instantiated, in here you may place some common logic to all your
Test Methods that should be run before any testing occurs.
Command line arguments can be parsed thanks to the twisted
@@ -181,8 +181,8 @@ To implement a simple ICMP ping based on this function you can do like so
return d
The arguments taken by self.sr() are exactly the same as the scapy send and
-receive function, the only difference is that instead of using the regualar
-scapy super socket it uses our twisted drivven wrapper around it.
+receive function, the only difference is that instead of using the regular
+scapy super socket it uses our twisted driven wrapper around it.
Alternatively this test can also be written using the
`twisted.defer.inlineCallbacks` decorator, that makes it look more similar to
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits