org/teams/AntiCensorshipTeam/SnowflakeBridgeSurvivalGuide.md

-== Bridge survival guide ==
+## Bridge survival guide
 
 SSH fingerprints:
 * `2048 SHA256:bP9tfPeIqkZkeKK1wcNT5t3CLyePz8oglFLRcdlP+gQ root@node (RSA)`
@@ -17,17 +17,17 @@ Upgrading snowflake-server. You need to give the new binary permission to bind p
 
 Check /var/log/syslog and /var/log/tor/snowflake-server.log for error messages. If snowflake-server.log shows `bind: permission denied`, ensure that you have run the `setcap` command, and that the `NoNewPrivileges=no` configuration from [[AntiCensorshipTeam/SnowflakeBridgeInstallationGuide]] is in place.
 
-=== Standalone proxy-go instances ===
+### Standalone proxy-go instances
 
 The standalone proxy-go instances are managed by runit. You can see a list of possible instances under `/etc/service`. They are set up to periodically restart themselves in case of a hang.
-{{{
+```
         sv status snowflake-proxy-standalone-17h        # check status
         sv start snowflake-proxy-standalone-17h  # start
         sv stop snowflake-proxy-standalone-17h   # stop
         ps xww | grep runsvdir  # check for error in the run script
-}}}
+```
 Logs are stored in `/home/snowflake-proxy/*.log.d`. Adding a new instance:
-{{{
+```
         cd /etc/runit
         mkdir -p my-instance/log
         cat > my-instance/run <<EOF
@@ -44,6 +44,6 @@ EOF
         mkdir /home/snowflake-proxy/my-instance.log.d
         chown snowflake-proxy:nogroup /home/snowflake-proxy/my-instance.log.d
         sv start my-instance
-}}}
+```
 
 Firewall configuration is in `/etc/ferm/ferm.conf`. Run `service ferm restart` after making changes.
\ No newline at end of file