[tor-commits] [community/master] Fix consistency across headers

[antonela@xxxxxxxxxxxxxx]

commit b2ca078543d9ad2c03cc0a6616a2be43f91e07a2
Author: Antonela <hola@xxxxxxxxxxx>
Date:   Mon Apr 13 13:12:22 2020 -0300

    Fix consistency across headers
    
    Close https://gitlab.torproject.org/torproject/web/community/-/issues/124
---
 content/relay-operations/technical-considerations/contents.lr    | 2 ++
 content/relay-operations/technical-setup/bridge/contents.lr      | 9 +++++----
 .../technical-setup/bridge/post-install/contents.lr              | 9 ++++++---
 .../relay-operations/technical-setup/post-install/contents.lr    | 5 ++++-
 4 files changed, 17 insertions(+), 8 deletions(-)

diff --git a/content/relay-operations/technical-considerations/contents.lr b/content/relay-operations/technical-considerations/contents.lr
index d2760c0..33ae63e 100644
--- a/content/relay-operations/technical-considerations/contents.lr
+++ b/content/relay-operations/technical-considerations/contents.lr
@@ -2,6 +2,8 @@ _model: page
 ---
 title: Technical considerations
 ---
+color: primary
+---
 _template: layout.html
 ---
 body:
diff --git a/content/relay-operations/technical-setup/bridge/contents.lr b/content/relay-operations/technical-setup/bridge/contents.lr
index c1175cd..54a8c35 100644
--- a/content/relay-operations/technical-setup/bridge/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/contents.lr
@@ -1,14 +1,12 @@
 _model: page
 ---
-title:
-
- Bridge
+title: Bridge
 ---
 body:
 
 This guide will help you set up an obfs4 bridge to help censored users connect to the Tor network. The requirements are:
 1. 24/7 Internet connectivity
-2. The ability to expose TCP ports to the Internet (make sure that NAT doesn't get in the way) 
+2. The ability to expose TCP ports to the Internet (make sure that NAT doesn't get in the way)
 
 Note: 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).
 ---
@@ -23,3 +21,6 @@ section_id: bridge-operations
 subtitle: Run an obfs4 bridge to help censored users connect to the Tor network
 ---
 _slug: {{bridge}}
+---
+color: primary
+---
diff --git a/content/relay-operations/technical-setup/bridge/post-install/contents.lr b/content/relay-operations/technical-setup/bridge/post-install/contents.lr
index d95da88..4abc2ea 100644
--- a/content/relay-operations/technical-setup/bridge/post-install/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/post-install/contents.lr
@@ -4,17 +4,17 @@ title: Post-install
 ---
 body:
 
-Congrats! 
+Congrats!
 
 If you get to this point, it means that your obfs4 bridge is running and is being distributed by BridgeDB to censored users. Note that it can take several days or weeks until you see a consistent set of users, so don't get discouraged if you don't see user connections right away. BridgeDB uses four buckets for bridge distribution: HTTPS, Moat, Email, and manual. Some buckets are used more than others, which also affects the time until your bridge sees users. Finally, there aren't many bridge users out there, so you cannot expect your bridge to be as popular as a relay.
 
-If you want to connect to your bridge manually, you will need to know the bridge's obfs4 certificate. See the file `/var/lib/tor/pt_state/obfs4_bridgeline.txt` and paste the entire bridge line into Tor Browser: 
+If you want to connect to your bridge manually, you will need to know the bridge's obfs4 certificate. See the file `/var/lib/tor/pt_state/obfs4_bridgeline.txt` and paste the entire bridge line into Tor Browser:
 
 ```
 Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=<CERTIFICATE> iat-mode=0
 ```
 
-You'll need to replace `<IP ADDRESS>`, `<PORT>`, and `<FINGERPRINT>` with the actual values, which you can find in the tor log. Make sure to use `<FINGERPRINT>`, not `<HASHED FINGERPRINT>`; and that `<PORT>` is the obfs4 port you chose - and not the OR port. 
+You'll need to replace `<IP ADDRESS>`, `<PORT>`, and `<FINGERPRINT>` with the actual values, which you can find in the tor log. Make sure to use `<FINGERPRINT>`, not `<HASHED FINGERPRINT>`; and that `<PORT>` is the obfs4 port you chose - and not the OR port.
 
 Finally, you can monitor your obfs4 bridge's usage on [Relay Search](https://metrics.torproject.org/rs.html#search).  Just enter your bridge's `<HASHED FINGERPRINT>` in the form and click "Search". After having set up the bridge, it takes approximately three hours for the bridge to show up in Relay Search.
 
@@ -24,3 +24,6 @@ html: two-columns-page.html
 key: 6
 ---
 subtitle: How to find your bridge in Relay Search and connect manually
+---
+color: primary
+---
diff --git a/content/relay-operations/technical-setup/post-install/contents.lr b/content/relay-operations/technical-setup/post-install/contents.lr
index 5236fbe..92441da 100644
--- a/content/relay-operations/technical-setup/post-install/contents.lr
+++ b/content/relay-operations/technical-setup/post-install/contents.lr
@@ -176,4 +176,7 @@ section: Relay operations
 ---
 section_id: relay-operations
 ---
-subtitle: 
+subtitle:
+---
+color: primary
+---

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