[tor-commits] [community/master] more corrections for https://gitlab.torproject.org/tpo/web/community/-/issues/206

emmapeel at torproject.org emmapeel at torproject.org
Sat Oct 9 18:20:39 UTC 2021


commit 5eaa7d0580dbdeb99f21f146afb0983a396b4755
Author: emma peel <emma.peel at riseup.net>
Date:   Sat Oct 9 20:20:28 2021 +0200

    more corrections for https://gitlab.torproject.org/tpo/web/community/-/issues/206
---
 content/onion-services/talk/contents.lr        | 2 +-
 content/relay/setup/bridge/netbsd/contents.lr  | 3 ++-
 content/relay/setup/bridge/windows/contents.lr | 3 ++-
 content/training/best-practices/contents.lr    | 4 ++--
 4 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/content/onion-services/talk/contents.lr b/content/onion-services/talk/contents.lr
index 07be9be..2105b36 100644
--- a/content/onion-services/talk/contents.lr
+++ b/content/onion-services/talk/contents.lr
@@ -116,7 +116,7 @@ OnionShare was developed after a human rights violation during the Snowden revel
 
 ### Decentralization
 
-As explained in [Overview](https://community.torproject.org/onion-services/overview/), there's no central authority that approves or rejects onion services.
+As explained in [Overview](../overview/), there's no central authority that approves or rejects onion services.
 The address of an onion service is automatically generated.
 Operators don't use the regular DNS infrastructure and do not need to purchase or register a domain name.
 
diff --git a/content/relay/setup/bridge/netbsd/contents.lr b/content/relay/setup/bridge/netbsd/contents.lr
index 37af844..7fab67b 100644
--- a/content/relay/setup/bridge/netbsd/contents.lr
+++ b/content/relay/setup/bridge/netbsd/contents.lr
@@ -84,7 +84,8 @@ To confirm your bridge is running with no issues, you should see something like
 
 ### 5. Final Notes
 
-If you are having troubles setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). If your bridge is now running, check out the [post-install notes](../post-install/).
+If you are having trouble setting up your bridge, have a look at [our help section](../../../getting-help/).
+If your bridge is now running, check out the [post-install notes](../../post-install/).
 
 ---
 subtitle: How to deploy an obfs4 bridge on NetBSD
diff --git a/content/relay/setup/bridge/windows/contents.lr b/content/relay/setup/bridge/windows/contents.lr
index 9b6a011..2d3260f 100644
--- a/content/relay/setup/bridge/windows/contents.lr
+++ b/content/relay/setup/bridge/windows/contents.lr
@@ -95,7 +95,8 @@ To confirm your bridge is running with no issues, you should see something like
 
 ### 6. Final notes
 
-If you are having troubles setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). If your bridge is now running, check out the [post-install notes](../post-install/).
+If you are having trouble setting up your bridge, have a look at [our help section](../../../getting-help/).
+If your bridge is now running, check out the [post-install notes](../../post-install/).
 
 ---
 subtitle: How to deploy an obfs4 bridge on Windows
diff --git a/content/training/best-practices/contents.lr b/content/training/best-practices/contents.lr
index 91bb2dd..c3c87a8 100644
--- a/content/training/best-practices/contents.lr
+++ b/content/training/best-practices/contents.lr
@@ -51,7 +51,7 @@ Once you've answered those questions, you're ready to plan your training!
    Will you be able to handle this alone? Or will you require partners?
    If you need more help, make sure the partners you're bringing in are aware of the safety needs of the community, and communicate with your contacts in the community to make sure they're okay with you bringing in additional trainers.
 7. Make sure your presentation is up-to-date (both information and screenshots) and save your presentation in two file formats -- for example, odp and pdf -- and on at least one additional device -- for example, on your computer and on a USB stick.
-8. Decide how you will facilitate a safer space. We recommend using the [Tor Code of Conduct](/training/code-of-conduct/).
+8. Decide how you will facilitate a safer space. We recommend using the [Tor Code of Conduct](../training/code-of-conduct/).
 
 You can also start the training by asking participants to come up with their own community agreements for the space.
 
@@ -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 resources at [community.torproject.org](https://community.torproject.org) and [support.torproject.org](https://support.torproject.org).
+6. Show the participants the retources 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



More information about the tor-commits mailing list