[tor-commits] [community/master] typo

2021-10-09 Thread emmapeel
commit a748d3a2a76376037ab58f7d7d3c380105ac0a47
Author: emma peel 
Date:   Sat Oct 9 20:54:49 2021 +0200

typo
---
 content/training/best-practices/contents.lr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/training/best-practices/contents.lr 
b/content/training/best-practices/contents.lr
index c3c87a8..43b83b5 100644
--- a/content/training/best-practices/contents.lr
+++ b/content/training/best-practices/contents.lr
@@ -62,7 +62,7 @@ You can also start the training by asking participants to 
come up with their own
 3. Communicate about when you'll take questions, either during the training, 
at the end, or both.
 4. Communicate about how you'll offer hands-on help (if at all).
 5. Communicate about how participants can contact you securely after the 
training.
-6. Show the participants the retources at [community.torproject.org](/) and 
[support.torproject.org](https://support.torproject.org).
+6. Show the participants the resources at [community.torproject.org](/) and 
[support.torproject.org](https://support.torproject.org).
 7. Show the participants other resources like 
[sec.eff.org](https://sec.eff.org).
 
 ## After the training

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits


[tor-commits] [community/master] typo

2021-06-22 Thread emmapeel
commit 3e78d6b1f8df7f319d66ceb4b4f9f243830679aa
Author: emma peel 
Date:   Tue Jun 22 16:59:16 2021 +0200

typo
---
 content/user-research/guidelines/contents.lr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/user-research/guidelines/contents.lr 
b/content/user-research/guidelines/contents.lr
index 159b0e7..2e57285 100644
--- a/content/user-research/guidelines/contents.lr
+++ b/content/user-research/guidelines/contents.lr
@@ -62,7 +62,7 @@ Thank the participant for their willingness to participate 
and explain that we a
 The interview should not last longer than 20 minutes.
 You can take notes on the printed material you will carry with you, or on your 
computer.
 
-While we're not interested in the specific charactersitics of individual 
participants, it's important for us to be able to determine the reach of our 
training sessions, usability workshops and interviews.
+While we're not interested in the specific characteristics of individual 
participants, it's important for us to be able to determine the reach of our 
training sessions, usability workshops and interviews.
 Distribute the demographics questionnaire among the participants, and help 
answer their questions about how to fill it in if they have any.
 
 Don't forget to thank the participant again at the end of the interview.

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits


[tor-commits] [community/master] typo. thanks AO for report

2021-05-18 Thread emmapeel
commit 25c20abcbae0fd23a64c3f72d479dad9086e8456
Author: emma peel 
Date:   Tue May 18 19:25:57 2021 +0200

typo. thanks AO for report
---
 content/relay/setup/bridge/contents.lr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/relay/setup/bridge/contents.lr 
b/content/relay/setup/bridge/contents.lr
index 9bfaa55..a3650df 100644
--- a/content/relay/setup/bridge/contents.lr
+++ b/content/relay/setup/bridge/contents.lr
@@ -10,7 +10,7 @@ This guide will help you set up an obfs4 bridge to help 
censored users connect t
 
 Note 1: If you're running a platform that is not listed on this page, you can 
[compile obfs4 from source](https://gitlab.com/yawning/obfs4#installation).
 
-Note 2: If you're planning to turn an existing but non-bridge relay into a 
bridge relay, changing IP address, name and fingerprint is advised to avoid 
easy discovery and blocklisting by ISP or governments.
+Note 2: If you're planning to turn an existing but non-bridge relay into a 
bridge relay, changing IP address, name and fingerprint is advised to avoid 
easy discovery and blocklisting by ISPs or governments.
 
 ---
 html: two-columns-page.html

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits


[tor-commits] [community/master] typo. thanks Bk__13 for the report

2021-05-18 Thread emmapeel
commit 6776b5c72fd75eb898955c75e0d94f62e7b8b7da
Author: emma peel 
Date:   Tue May 18 19:19:27 2021 +0200

typo. thanks Bk__13 for the report
---
 content/relay/setup/exit/contents.lr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/relay/setup/exit/contents.lr 
b/content/relay/setup/exit/contents.lr
index 5b17ec7..df21cb1 100644
--- a/content/relay/setup/exit/contents.lr
+++ b/content/relay/setup/exit/contents.lr
@@ -22,7 +22,7 @@ Do not mix your own traffic with your exit relay traffic.
 
 ## Reverse DNS and WHOIS record
 
-Before turning your non-exit relay into an exit relay, ensure that you have 
set a reverse DNS record (PTR) to make it more obvious that this is a tor exit 
relay. Something like "tor-exit" it its name is a good start.
+Before turning your non-exit relay into an exit relay, ensure that you have 
set a reverse DNS record (PTR) to make it more obvious that this is a tor exit 
relay. Something like "tor-exit" in its name is a good start.
 
 If your provider offers it, make sure your WHOIS record contains clear 
indications that this is a Tor exit relay.
 

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits


[tor-commits] [community/master] typo

2021-05-18 Thread emmapeel
commit bea01e7b50cc130f6f0ea1e938079db3ff80c7f2
Author: emma peel 
Date:   Tue May 18 13:44:57 2021 +0200

typo
---
 content/user-research/guidelines/contents.lr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/user-research/guidelines/contents.lr 
b/content/user-research/guidelines/contents.lr
index c78ca5e..6d13142 100644
--- a/content/user-research/guidelines/contents.lr
+++ b/content/user-research/guidelines/contents.lr
@@ -31,7 +31,7 @@ When we are in Tor training, we listen to the stories people 
tell us about their
 ## Describe and Ask for consent
 We don't collect names or contact details of interview participants, and any 
time you're going to receive impressions, surveys, or records, you should ask 
for their consent to participate - this should be recorded or registered in the 
form.
 
-You'd love to read about your experiences during the training, product 
testing, and interviews. There are a few ways to do this:
+We'd love to read about your experiences during the training, product testing, 
and interviews. There are a few ways to do this:
 
 * Scenario: describe the process of the test you ran.
 * Demographics: While we are not interested in specific characteristics of our 
audience, or binary attributes, we must know the total reach of your Tor 
training. You should take [this material]() with you on the day of your 
research, distribute it among participants, and answer their questions about 
how to fill it in if they have any.



___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits


[tor-commits] [community/master] typo

2021-05-17 Thread emmapeel
commit 2e3511f706841922dba1f45315ac0f34b1b99c1f
Author: emma peel 
Date:   Mon May 17 19:51:39 2021 +

typo
---
 content/relay-operations/technical-setup/snowflake/browser/contents.lr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/content/relay-operations/technical-setup/snowflake/browser/contents.lr 
b/content/relay-operations/technical-setup/snowflake/browser/contents.lr
index 3d4c8d7..dc7e954 100644
--- a/content/relay-operations/technical-setup/snowflake/browser/contents.lr
+++ b/content/relay-operations/technical-setup/snowflake/browser/contents.lr
@@ -14,7 +14,7 @@ There are very few requirements to running a browser-based 
proxy:
 ### 1. Install the Snowflake addon to your browser
 
 If you are running Firefox, you can install our [Firefox 
addon](https://addons.mozilla.org/en-US/firefox/addon/torproject-snowflake/).
-Chome users can install our addon from the [Google 
webstore](https://chrome.google.com/webstore/detail/snowflake/mafpmfcccpbjnhfhjnllmmalhifmlcie).
+Chrome users can install our addon from the [Google 
webstore](https://chrome.google.com/webstore/detail/snowflake/mafpmfcccpbjnhfhjnllmmalhifmlcie).
 
 Once it is installed, you can toggle the `Enabled` switch to turn it off and 
on.
 It's easiest to leave it running while you browse and it should not interfere 
with your regular browsing experience.

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits


[tor-commits] [community/master] typo.

2019-09-11 Thread emmapeel
commit bcc60b133cc2b06259261e061eb1b116a00463b6
Merge: ee0a98f 4bffa96
Author: emma peel 
Date:   Wed Sep 11 12:32:06 2019 +0200

typo.
closes https://github.com/torproject/community/pull/10

 .../relay-operations/technical-setup/guard/freebsd/updates/contents.lr  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits


[tor-commits] [community/master] typo

2019-08-21 Thread emmapeel
commit 78e52e3bfa5ff0bdd6d0c92eb234aa2e344f9dc4
Author: emma peel 
Date:   Wed Aug 21 19:43:36 2019 +0200

typo
---
 content/localization/translation-problem/contents.lr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/localization/translation-problem/contents.lr 
b/content/localization/translation-problem/contents.lr
index a4be60d..6194625 100644
--- a/content/localization/translation-problem/contents.lr
+++ b/content/localization/translation-problem/contents.lr
@@ -18,7 +18,7 @@ body:
 
 ### Reporting an error with a translation
 
-* If you are already a [Tor translator](becoming-tor-translator), you can 
simply find the string and fix it 
[transifex](https://www.transifex.com/otf/torproject/).
+* If you are already a [Tor translator](becoming-tor-translator), you can 
simply find the string and fix it in 
[transifex](https://www.transifex.com/otf/torproject/).
 * If you don't know how to find the string to fix, you can [open a ticket on 
our 
Bugtracker](https://trac.torproject.org/projects/tor/wiki/doc/community/HowToReportBugFeedback),
 under the **Community/Translations** component.
 * You can report such issues on [irc](https://webchat.oftc.net/), on the 
#tor-l10n channel (you may need to be registered to log in).
 * You can send an email to the [tor localization mailing 
list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-l10n).

___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits