[tor-commits] [translation/support-censorship] pulling translations from transifex

Fri Apr 6 23:28:06 UTC 2018

commit f0b627c73ebe13e1d5b9ce9f0e0d3af38bc505c8
Author: Translation commit bot <translation at torproject.org>
Date:   Fri Apr 6 23:28:00 2018 +0000

    pulling translations from transifex
---
 ach.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 ady.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 af.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ak.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 am.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ar.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 arn.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 ast.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 az.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ba.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 be.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 bg.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 bn.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 bn_BD.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 bn_IN.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 bo.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 br.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 brx.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 bs.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ca.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ceb.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 cs.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 csb.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 cv.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 cy.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 da.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 de.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 dz.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 el.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 en_GB.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 eo.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 es.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 es_AR.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 es_CL.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 es_CO.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 es_MX.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 et.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 eu.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 fa.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 fi.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 fil.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 fo.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 fr.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 fr_CA.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 fur.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 fy.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ga.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 gd.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 gl.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 gu.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 gu_IN.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 gun.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 ha.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 he.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 hi.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 hr.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 hr_HR.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 ht.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 hu.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 hy.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ia.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 id.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 is.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 it.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ja.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 jv.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ka.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 kk.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 km.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 kn.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ko.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ko_KR.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 ku.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ku_IQ.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 kw.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ky.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 la.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 lb.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 lg.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ln.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 lo.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 lt.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 lv.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 mg.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 mi.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 mk.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ml.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 mn.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 mr.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ms_MY.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 mt.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 my.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 nah.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 nap.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 nb.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 nds.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 ne.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 nl.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 nl_BE.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 nn.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 nso.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 oc.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 om.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 or.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 pa.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 pap.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 pl.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 pms.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 ps.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 pt.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 pt_BR.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 ro.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ru.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ru at petr1708.json        | 40 ++++++++++++++++++++++++++++++++++++++++
 scn.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 sco.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 si_LK.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 sk.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 sk_SK.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 sl.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 sl_SI.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 sn.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 so.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 son.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 sq.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 sr.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 sr at latin.json           | 40 ++++++++++++++++++++++++++++++++++++++++
 st.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 su.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 support-censorship.json | 40 ++++++++++++++++++++++++++++++++++++++++
 sv.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 sw.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 szl.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 ta.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 te.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 te_IN.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 tg.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 th.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ti.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 tk.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 tr.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 tzm.json                | 40 ++++++++++++++++++++++++++++++++++++++++
 ug at Arab.json            | 40 ++++++++++++++++++++++++++++++++++++++++
 uk.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ur.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ur_PK.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 uz.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 ve.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 vi.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 wa.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 wo.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 zh_CN.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 zh_HK.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 zh_TW.json              | 40 ++++++++++++++++++++++++++++++++++++++++
 zu.json                 | 40 ++++++++++++++++++++++++++++++++++++++++
 155 files changed, 6200 insertions(+)

diff --git a/ach.json b/ach.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ach.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ady.json b/ady.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ady.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/af.json b/af.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/af.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ak.json b/ak.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ak.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/am.json b/am.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/am.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ar.json b/ar.json
new file mode 100644
index 000000000..f8e8feb7f
--- /dev/null
+++ b/ar.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "كيف يمكنني تنزيل تور إن كان موقع torproject.org محجوبًا ؟",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "أواجه صعوبة في الإتصال بشبكة تور ولا أدري أين تكمن المُشكلة.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/arn.json b/arn.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/arn.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ast.json b/ast.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ast.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/az.json b/az.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/az.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ba.json b/ba.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ba.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/be.json b/be.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/be.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/bg.json b/bg.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/bg.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/bn.json b/bn.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/bn.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/bn_BD.json b/bn_BD.json
new file mode 100644
index 000000000..d5005ce06
--- /dev/null
+++ b/bn_BD.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "# সেন্সরশিপ-1",
+	"control": "সেন্সরশিপ-1",
+	"title": "আমাদের ওয়েবসাইট একটি সেন্সর দ্বারা অবরুদ্ধ হয়। টর ব্রাউজার কি আমাদের ওয়েবসাইট অ্যাক্সেস করতে ব্যবহারকারীদের সাহায্য করতে পারেন?",
+	"description": "<p class=\"mb-3\">টর ব্রাউজার অবশ্যই  মানুষকে সাহায্য করতে পারে আপনার ওয়েবসাইটে অ্যাক্সেস করতে যেখানে এটি অবরুদ্ধ রয়েছে।বেশিরভাগ সময়,<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\"> à¦Ÿà¦° à¦¬à§à¦°à¦¾à¦‰à¦œà¦¾à¦° à¦¡à¦¾à¦‰à¦¨à¦²à§‹à¦¡ à¦•à¦°à¦¾ </a></mark>à¦à¦¬à¦‚ à¦¤à¦¾à¦°à¦ªà¦° à¦à¦Ÿà¦¿ à¦¬à§à¦²à¦• à¦•à¦°à¦¾ à¦¸à¦¾à¦‡à¦Ÿà§‡ à¦¨à§‡à¦à¦¿à¦—à§‡à¦Ÿ à¦•à¦°à¦¾à¦° à¦œà¦¨à§à¦¯ à¦…à§à¦¯à¦¾à¦•à§à¦¸à§‡à¦¸à§‡à¦° à¦…à¦¨à§à¦®à¦¤à¦¿ à¦¦à§‡à¦¬à§‡à¥¤  à¦¯à§‡ à¦œà¦¾à¦¯à¦¼à¦—à¦¾à¦¯à¦¼ à¦ªà§à¦°à¦šà§à¦° à¦¸à§‡à¦¨à§à¦¸à¦°à¦¶à¦¿à¦ª à¦°à¦¯à¦¼à§‡à¦›à§‡, à¦¤à¦¾  à¦…à§à¦¯à¦¾à¦•à§à¦¸à§‡à¦¸à§‡à¦° à¦œà¦¨à§à¦¯ à¦†à¦®à¦¾à¦¦à§‡à¦° à¦•à¦¾à¦›à§‡ à¦ªà§à¦°à¦šà§à¦° à¦ªà¦°à¦¿à¦®à¦¾à¦£à§‡ à¦¸à§‡à¦¨à§à¦¸à¦°à¦¶à¦¿à¦ª  à¦ªà§à¦°à¦¤à¦¾à¦°à¦£à¦¾ à¦¬à¦¿à¦•à¦²à§à
 ¦ª à¦†à¦›à§‡, <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">প্ল্যাগেবল ট্রান্সপোর্টগুলি সহ এমন</a></mark>।আরো তথ্যের জন্য, দেখুন টর ব্রাউজার ইউজার ম্যানুয়াল<a href=\"https://tb-manual.torproject.org/en-US/\"><mark> বিভাগ<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\"> সেন্সরশিপের উপর</a></mark>।</p>"
+    },
+    "censorship-2": {
+	"id": "# সেন্সরশিপ-2",
+	"control": "সেন্সরশিপ-2",
+	"title": "আমার প্রিয় ওয়েবসাইট টর পর্যন্ত অ্যাক্সেস অবরুদ্ধ করছে",
+	"description": "<p class=\"mb-3\">à¦¶à§à¦¨à§‡ à¦¦à§à¦ƒà¦–à¦¿à¦¤ à¦¯à§‡ à¦†à¦ªà¦¨à¦¿ à¦¯à§‡ à¦“à¦¯à¦¼à§‡à¦¬à¦¸à¦¾à¦‡à¦Ÿà¦Ÿà¦¿ à¦šà¦¾à¦¨ à¦¤à¦¾ à¦¦à§‡à¦–à¦¤à§‡ à¦ªà¦¾à¦°à¦¬à§‡à¦¨ à¦¨à¦¾! à¦•à¦–à¦¨à¦“ à¦•à¦–à¦¨à¦“ à¦“à¦¯à¦¼à§‡à¦¬à¦¸à¦¾à¦‡à¦Ÿ à¦Ÿà¦° à¦¬à§à¦¯à¦¬à¦¹à¦¾à¦°à¦•à¦¾à¦°à§€à¦¦à§‡à¦° à¦…à¦¬à¦°à§‹à¦§ à¦•à¦°à¦¬à§‡ à¦•à¦¾à¦°à¦£ à¦¤à¦¾à¦°à¦¾ à¦—à¦¡à¦¼ à¦Ÿà¦° à¦¬à§à¦¯à¦¬à¦¹à¦¾à¦°à¦•à¦¾à¦°à§€ à¦à¦¬à¦‚ à¦¸à§à¦¬à¦¯à¦¼à¦‚à¦•à§à¦°à¦¿à¦¯à¦¼ à¦Ÿà§à¦°à§à¦¯à¦¾à¦«à¦¿à¦•à§‡à¦° à¦®à¦§à§à¦¯à§‡ à¦ªà¦¾à¦°à§à¦¥à¦•à§à¦¯ à¦¬à¦²à¦¤à§‡ à¦ªà¦¾à¦°à§‡ à¦¨à¦¾à¥¤ à¦Ÿà¦° à¦¬à§à¦¯à¦¬à¦¹à¦¾à¦°à¦•à¦¾à¦°à§€à¦¦à§‡à¦° à¦…à¦¬à¦°à§‹à¦§ à¦•à¦°à¦¾ à¦¸à¦¾à¦‡à¦Ÿà¦—à§à¦²à§‹à¦¤à§‡ à¦†à¦®à¦°à¦¾ à¦¯à§‡ à¦¸à¦«à¦²à¦¤à¦¾ à¦ªà§‡à¦¯à¦¼à§‡à¦›à¦¿ à¦¤à¦¾ à¦¬à§à¦¯à¦¬à¦¹à¦¾à¦°à¦•à¦¾à¦°à§€à¦¦à§‡à¦° à¦¸à¦¾à¦‡à¦Ÿà§‡ à¦¸à¦°à¦¾à¦¸à¦°à¦¿ à¦ªà§à¦°à¦¶à¦¾à¦¸à¦•à§‡à¦° à¦¸à¦¾à¦¥à§‡ à¦¯à§‹à¦—à¦¾à¦¯à§‹à¦— à¦•à¦°à¦¤à§‡ à¦ªà¦¾à¦°à§‡à¥¤ à¦à¦‡ à¦§à¦°à¦£à§‡à¦° à¦•à¦¿à¦›à§ à¦¹à¦¯à¦¼à¦¤à§‹ à¦à¦‡ à¦•à§Œà¦¶à¦²à¦Ÿà¦¿ à¦•à¦°à¦¤à§‡ à¦ªà¦¾à¦
 °à§‡: \"à¦¹à¦¾à¦‡! à¦†à¦®à¦¿ à¦Ÿà¦¾à¦¯à¦¼à¦¾à¦° à¦¬à§à¦°à¦¾à¦‰à¦œà¦¾à¦° à¦¬à§à¦¯à¦¬à¦¹à¦¾à¦° à¦•à¦°à¦¾à¦° à¦¸à¦®à¦¯à¦¼ à¦†à¦ªà¦¨à¦¾à¦° à¦¸à¦¾à¦‡à¦Ÿ xyz.com à¦…à§à¦¯à¦¾à¦•à§à¦¸à§‡à¦¸ à¦•à¦°à¦¾à¦° à¦šà§‡à¦·à§à¦Ÿà¦¾ à¦•à¦°à§‡à¦›à¦¿ à¦à¦¬à¦‚ à¦†à¦¬à¦¿à¦·à§à¦•à¦¾à¦° à¦•à¦°à§‡à¦›à¦¿ à¦¯à§‡ à¦†à¦ªà¦¨à¦¿ à¦Ÿà¦° à¦¬à§à¦¯à¦¬à¦¹à¦¾à¦°à¦•à¦¾à¦°à§€à¦¦à§‡à¦° à¦†à¦ªà¦¨à¦¾à¦° à¦¸à¦¾à¦‡à¦Ÿ à¦…à§à¦¯à¦¾à¦•à§à¦¸à§‡à¦¸ à¦•à¦°à¦¾à¦° à¦…à¦¨à§à¦®à¦¤à¦¿ à¦¦à¦¿à¦šà§à¦›à§‡à¦¨ à¦¨à¦¾à¥¤ à¦†à¦®à¦¿ à¦†à¦ªà¦¨à¦¾à¦•à§‡ à¦à¦‡ à¦¸à¦¿à¦¦à§à¦§à¦¾à¦¨à§à¦¤à§‡à¦° à¦ªà§à¦¨à¦°à§à¦¬à¦¿à¦¬à§‡à¦šà¦¨à¦¾ à¦•à¦°à¦¾à¦° à¦…à¦¨à§à¦°à§‹à¦§ à¦•à¦°à¦›à¦¿; à¦¸à¦¾à¦°à¦¾ à¦¬à¦¿à¦¶à§à¦¬à§‡à¦° à¦®à¦¾à¦¨à§à¦· à¦¤à¦¾à¦¦à§‡à¦° à¦—à§‹à¦ªà¦¨à§€à¦¯à¦¼à¦¤à¦¾ à¦°à¦•à§à¦·à¦¾ à¦à¦¬à¦‚ à¦¸à§‡à¦¨à§à¦¸à¦°à¦¶à¦¿à¦ªà§‡à¦° à¦¬à¦¿à¦°à§à¦¦à§à¦§à§‡ à¦²à¦¡à¦¼à¦¾à¦‡ à¦•à¦°à§‡à¥¤ à¦Ÿà¦° à¦¬à§à¦¯à¦¬à¦¹à¦¾à¦°à¦•à¦¾à¦°à§€à¦¦à§‡à¦° à¦¬à§à¦²à¦• à¦•à¦°à§‡, à¦†à¦ªà¦¨à¦¿ à¦¸à¦®à§à¦à¦¬à¦¤ à¦¦à¦®à¦¨à¦®à§‚à¦²à¦• à¦¦à§‡à¦¶à¦—à§à¦²à¦¿à¦¤à§‡ à¦²
 à§‹à¦•à§‡à¦¦à§‡à¦°à¦•à§‡ à¦¬à§à¦²à¦• à¦•à¦°à§‡ à¦¦à¦¿à¦šà§à¦›à§‡à¦¨ à¦¯à¦¾à¦°à¦¾ à¦à¦•à¦Ÿà¦¿ à¦«à§à¦°à¦¿ à¦‡à¦¨à§à¦Ÿà¦¾à¦°à¦¨à§‡à¦Ÿ, à¦¸à¦¾à¦‚à¦¬à¦¾à¦¦à¦¿à¦• à¦à¦¬à¦‚ à¦—à¦¬à§‡à¦·à¦• à¦¯à¦¾à¦°à¦¾ à¦¨à¦¿à¦œà§‡à¦¦à§‡à¦° à¦†à¦¬à¦¿à¦·à§à¦•à¦¾à¦°, à¦¹à§à¦‡à¦¸à¦² à¦¬à§à¦²à§‹à¦¯à¦¼à¦¾à¦°, à¦…à§à¦¯à¦¾à¦•à§à¦Ÿà¦¿à¦à¦¿à¦¸à§à¦Ÿ, à¦à¦¬à¦‚ à¦¸à¦¾à¦§à¦¾à¦°à¦£ à¦®à¦¾à¦¨à§à¦· à¦¯à¦¾à¦°à¦¾ à¦†à¦•à§à¦°à¦®à¦£à¦¾à¦¤à§à¦®à¦• à¦¤à§ƒà¦¤à§€à¦¯à¦¼ à¦ªà¦•à§à¦·à§‡à¦° à¦Ÿà§à¦°à§à¦¯à¦¾à¦•à¦¿à¦‚ à¦¥à§‡à¦•à§‡ à¦…à¦ªà§à¦Ÿ à¦†à¦‰à¦Ÿ à¦•à¦°à¦¤à§‡ à¦šà¦¾à¦¨ à¦¦à¦¯à¦¼à¦¾ à¦•à¦°à§‡ à¦¡à¦¿à¦œà¦¿à¦Ÿà¦¾à¦² à¦—à§‹à¦ªà¦¨à§€à¦¯à¦¼à¦¤à¦¾ à¦à¦¬à¦‚ à¦‡à¦¨à§à¦Ÿà¦¾à¦°à¦¨à§‡à¦Ÿ à¦¸à§à¦¬à¦¾à¦§à§€à¦¨à¦¤à¦¾à¦° à¦ªà¦•à§à¦·à§‡ à¦¦à§ƒà¦¢à¦¼ à¦…à¦¬à¦¸à§à¦¥à¦¾à¦¨ à¦¨à¦¿à¦¨ à¦à¦¬à¦‚ à¦Ÿà¦° à¦¬à§à¦¯à¦¬à¦¹à¦¾à¦°à¦•à¦¾à¦°à§€à¦¦à§‡à¦° xyz.com à¦…à§à¦¯à¦¾à¦•à§à¦¸à§‡à¦¸à§‡à¦° à¦…à¦¨à§à¦®à¦¤à¦¿ à¦¦à¦¿à¦¨à¥¤ à¦§à¦¨à§à¦¯à¦¬à¦¾à¦¦à¥¤ \"à¦¬à§à¦¯à¦¾à¦‚à¦•à¦—à§à¦²à¦¿à¦° à¦•à§à¦·à§‡à¦¤à§à¦°à§‡ à¦à¦¬à¦‚ à¦…à¦¨à§à¦¯à¦
 ¾à¦¨à§à¦¯ à¦¸à¦‚à¦¬à§‡à¦¦à¦¨à¦¶à§€à¦² à¦“à¦¯à¦¼à§‡à¦¬à¦¸à¦¾à¦‡à¦Ÿà¦—à§à¦²à¦¿, à¦à¦Ÿà¦¿ à¦à§‚à¦—à§‹à¦²-à¦à¦¿à¦¤à§à¦¤à¦¿à¦• à¦¬à§à¦²à¦•à¦¿à¦‚ à¦¦à§‡à¦–à¦¤à§‡ à¦¸à¦¾à¦§à¦¾à¦°à¦£ (à¦¯à¦¦à¦¿ à¦à¦•à¦Ÿà¦¿ à¦¬à§à¦¯à¦¾à¦‚à¦• à¦œà¦¾à¦¨à§‡ à¦¯à§‡ à¦†à¦ªà¦¨à¦¿ à¦¸à¦¾à¦§à¦¾à¦°à¦£à¦¤ à¦à¦• à¦¦à§‡à¦¶ à¦¥à§‡à¦•à§‡ à¦¤à¦¾à¦¦à§‡à¦° à¦ªà¦°à¦¿à¦·à§‡à¦¬à¦¾à¦—à§à¦²à¦¿ à¦…à§à¦¯à¦¾à¦•à§à¦¸à§‡à¦¸ à¦•à¦°à§‡à¦¨, à¦à¦¬à¦‚ à¦¹à¦ à¦¾à§Ž à¦†à¦ªà¦¨à¦¿ à¦¬à¦¿à¦¶à§à¦¬à§‡à¦° à¦…à¦¨à§à¦¯ à¦ªà§à¦°à¦¾à¦¨à§à¦¤à§‡ à¦à¦•à¦Ÿà¦¿ à¦ªà§à¦°à¦¸à§à¦¥à¦¾à¦¨ à¦°à¦¿à¦²à§‡ à¦¥à§‡à¦•à§‡ à¦¸à¦‚à¦¯à§‹à¦— à¦•à¦°à¦›à§‡à¦¨, à¦†à¦ªà¦¨à¦¾à¦° à¦…à§à¦¯à¦¾à¦•à¦¾à¦‰à¦¨à§à¦Ÿ à¦²à¦• à¦•à¦°à¦¾ à¦¹à¦¤à§‡ à¦ªà¦¾à¦°à§‡ à¦¬à¦¾à¦¸à§à¦¥à¦—à¦¿à¦¤). à¦¯à¦¦à¦¿ à¦†à¦ªà¦¨à¦¿ à¦à¦•à¦Ÿà¦¿ à¦ªà§‡à¦à¦¯à¦¼à¦¾à¦œ à¦ªà¦°à¦¿à¦·à§‡à¦¬à¦¾ à¦¸à¦¾à¦¥à§‡ à¦¸à¦‚à¦¯à§‹à¦— à¦•à¦°à¦¤à§‡ à¦…à¦•à§à¦·à¦® à¦¹à¦¨, à¦¤à¦¬à§‡ à¦¦à¦¯à¦¼à¦¾ à¦•à¦°à§‡ à¦¦à§‡à¦–à§à¦¨ à¦†à¦®à¦¿ X.onion à¦¤à§‡ à¦ªà§Œà¦à¦›à¦¾à¦¤à§‡ à¦ªà¦¾à¦°à¦¿ à¦¨à¦¾!"
+    },
+    "censorship-3": {
+	"id": "#সেন্সরশিপ-3",
+	"control": "সেন্সরশিপ-3",
+	"title": "Torproject.org ব্লক করলে আমি কিভাবে টর ডাউনলোড করব?",
+	"description": "<p class=\"mb-3\">যদি আপনি আমাদের<mark><a href=\"https://www.torproject.org\"> ওয়েবসাইটের মাধ্যমে</a></mark> টর ডাউনলোড করতে না পারেন, আপনি GetTor এর মাধ্যমে আপনাকে বিতরণ করা টর একটি কপি পেতে পারেন। GetTor হল একটি পরিষেবা যা স্বয়ংক্রিয়ভাবে টর ব্রাউজারের সর্বশেষ সংস্করণে লিংকযুক্ত বার্তাগুলিতে প্রতিক্রিয়া দেয়, বিভিন্ন স্থানে অবস্থান নেয় যা সেন্সর হওয়ার সম্ভাবনা কম থাকে, যেমন ড্রপবক্স, Google ড্রাইভ, এবং জিথাব।</p>"
+    },
+    "censorship-4": {
+	"id": "# সেন্সরশিপ -4",
+	"control": "সেন্সরশিপ -4",
+	"title": "আমি টর ব্রাউজারে সংযোগ করতে পারছি না, আমার নেটওয়ার্ক সেন্সর করা হয়েছে?",
+	"description": "<p class=\"mb-3\">আপনি একটি সেন্সর নেটওয়ার্কে হতে পারেন, এবং তাই আপনার সেতু ব্যবহার করে চেষ্টা করা উচিত। কিছু ব্রিজ টর ব্রাউজার এর মধ্যে নির্মিত হয়, এবং আপনি টর লঞ্চার উইন্ডোতে \"কনফিগার\" (তারপর প্রম্পট অনুসরণ) নির্বাচন করে সেতু ব্যবহার করতে পারেন যা আপনি যখন প্রথমবারের জন্য টর ব্রাউজার খুলেন তখন পপ-আপ হিসেবে আসে। আপনার যদি অন্যান্য সেতুর প্রয়োজন হয়, তাহলে আপনি <mark><a href=\"https://bridges.torproject.or
 g/\">আমাদের ব্রিজেস ওয়েবসাইটে </a></mark>তাদের পেতে পারেন। সেতু সম্পর্কে আরও তথ্যের জন্য, <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">টর ব্রাউজার ম্যানুয়াল দেখুন</a></mark>।</p>"
+    },
+    "censorship-5": {
+	"id": "# সেন্সরশিপ-5",
+	"control": "সেন্সরশিপ-5",
+	"title": "আমি টর সংযোগে সমস্যা হচ্ছে, এবং আমি কি ভুল বুঝতে পারছি না।",
+	"description": "<p class=\"mb-3\">à¦¯à¦¦à¦¿ à¦†à¦ªà¦¨à¦¾à¦° à¦¸à¦‚à¦¯à§‹à¦—à§‡à¦° à¦¸à¦®à¦¸à§à¦¯à¦¾ à¦¹à¦¯à¦¼ à¦¤à¦¬à§‡ à¦¦à¦¯à¦¼à¦¾ à¦•à¦°à§‡ \"à¦Ÿà¦° à¦²à¦— à¦•à§à¦²à¦¿à¦ªà¦¬à§‹à¦°à§à¦¡à§‡ à¦•à¦ªà¦¿ à¦•à¦°à§à¦¨\" à¦¬à¦¿à¦•à¦²à§à¦ªà¦Ÿà¦¿ à¦¨à¦¿à¦°à§à¦¬à¦¾à¦šà¦¨ à¦•à¦°à§à¦¨à¥¤ à¦à¦°à¦ªà¦° à¦Ÿà¦°  à¦²à¦— à¦à¦•à¦Ÿà¦¿ à¦ªà¦¾à¦ à§à¦¯ à¦«à¦¾à¦‡à¦² à¦¬à¦¾ à¦…à¦¨à§à¦¯ à¦¨à¦¥à¦¿à¦¤à§‡ à¦ªà§‡à¦¸à§à¦Ÿ à¦•à¦°à§à¦¨à¥¤ à¦†à¦ªà¦¨à¦¿ à¦à¦‡ à¦¸à¦¾à¦§à¦¾à¦°à¦£ à¦²à¦— à¦¤à§à¦°à§à¦Ÿà¦¿à¦—à§à¦²à¦¿à¦° à¦à¦•à¦Ÿà¦¿ à¦¦à§‡à¦–à¦¤à§‡ à¦ªà¦¾à¦¬à§‡à¦¨ (à¦†à¦ªà¦¨à¦¾à¦° à¦Ÿà¦° à¦²à¦—à¦—à§à¦²à¦¿à¦¤à§‡ à¦¨à¦¿à¦®à§à¦¨à¦²à¦¿à¦–à¦¿à¦¤ à¦²à¦¾à¦‡à¦¨à¦—à§à¦²à¦¿ à¦¦à§‡à¦–à§à¦¨): <h5>à¦¸à¦¾à¦§à¦¾à¦°à¦£ à¦²à¦— à¦¤à§à¦°à§à¦Ÿà¦¿ # 1: à¦ªà§à¦°à¦•à§à¦¸à¦¿ à¦¸à¦‚à¦¯à§‹à¦— à¦¬à§à¦¯à¦°à§à¦¥à¦¤à¦¾ 2017-10-29 09:23:40.800 [à¦¬à¦¿à¦œà§à¦žà¦ªà§à¦¤à¦¿] 127.0.0.1:9150 à¦à¦° à¦‰à¦ªà¦° à¦¸à¦•à§à¦¸ à¦²à¦¿à¦¸à§‡à¦¨à¦¾à¦° à¦†à¦°à¦®à§à¦ à¦•à¦°à§à¦¨\n2017-10-29 09: 23: 47.900 [à¦¬à¦¿à¦œà§à¦žà¦ªà§à¦¤à¦¿] à
 ¦¬à§à¦Ÿà¦¸à§à¦Ÿà§à¦°à§à¦¯à¦¾à¦ª 5%: à¦¡à¦¿à¦°à§‡à¦•à§à¦Ÿà¦°à¦¿ à¦¸à¦¾à¦°à§à¦à¦¾à¦°à§‡ à¦¸à¦‚à¦¯à§à¦•à§à¦¤ à¦¹à¦šà§à¦›à§‡\n 2017-10-29 09: 23: 47.900 [à¦¬à¦¿à¦œà§à¦žà¦ªà§à¦¤à¦¿] à¦¬à§à¦Ÿà¦¸à§à¦Ÿà§à¦°à§à¦¯à¦¾à¦ª à¦•à¦°à¦¾ 10%: à¦¡à¦¿à¦°à§‡à¦•à§à¦Ÿà¦°à¦¿ à¦¸à¦¾à¦°à§à¦à¦¾à¦°à§‡à¦° à¦¸à¦¾à¦¥à§‡ à¦¹à§à¦¯à¦¾à¦¨à§à¦¡à¦¶à§‡à¦•à¦¿à¦‚ à¦¸à¦®à¦¾à¦ªà§à¦¤ à¦•à¦°à¦¾ \n2017- 10-29 09: 24: 08.900 [à¦“à¦¯à¦¼à¦¾à¦°à§à¦¨] à¦ªà§à¦°à¦•à§à¦¸à¦¿ à¦•à§à¦²à¦¾à¦¯à¦¼à§‡à¦¨à§à¦Ÿ: xx..xxx..xxx.xx: xxxxx (\"à¦¸à¦¾à¦§à¦¾à¦°à¦£ à¦¸à¦•à¦¸ à¦¸à¦¾à¦°à§à¦à¦¾à¦° à¦¬à§à¦¯à¦°à§à¦¥à¦¤à¦¾\") à¦¸à¦¾à¦¥à§‡ à¦¸à¦‚à¦¯à§à¦•à§à¦¤ à¦•à¦°à¦¤à§‡ à¦…à¦•à§à¦·à¦®à¥¤ 2017-10-29 09: 24: 08.900 [à¦“à¦¯à¦¼à¦¾à¦°à§à¦¡ ] à¦ªà§à¦°à¦•à§à¦¸à¦¿ à¦•à§à¦²à¦¾à¦¯à¦¼à§‡à¦¨à§à¦Ÿ: xx..xxx..xxx.xx: XXXxx à¦à¦°(\"à¦¸à¦¾à¦§à¦¾à¦°à¦£ SOCKS à¦¸à¦¾à¦°à§à¦à¦¾à¦° à¦¬à§à¦¯à¦°à§à¦¥à¦¤à¦¾\")à¦¸à¦¾à¦¥à§‡ à¦¸à¦‚à¦¯à§à¦•à§à¦¤ à¦•à¦°à¦¤à§‡ à¦…à¦•à§à¦·à¦®à¥¤\n2017-10-29 09: 24: 08.900 [à¦“à¦¯à¦¼à¦¾à¦°à§à¦¨] à¦ªà§à¦°à¦•à
 §à¦¸à¦¿ à¦•à§à¦²à¦¾à¦¯à¦¼à§‡à¦¨à§à¦Ÿ: xxx..xxx.xx: xxxxx (\"à¦¸à¦¾à¦§à¦¾à¦°à¦£ SOCKS à¦¸à¦¾à¦°à§à¦à¦¾à¦° à¦¬à§à¦¯à¦°à§à¦¥à¦¤à¦¾\")<code><pre><p class=\"mb-3\"><p class=\"mb-3\">à¦à¦° à¦¸à¦¾à¦¥à§‡ à¦¸à¦‚à¦¯à§à¦•à§à¦¤ à¦•à¦°à¦¤à§‡ à¦…à¦•à§à¦·à¦®à¥¤ à¦¯à¦¦à¦¿ à¦†à¦ªà¦¨à¦¿ à¦†à¦ªà¦¨à¦¾à¦° à¦Ÿà¦° â€‹â€‹à¦²à¦—à§‡ à¦à¦°à¦•à¦® à¦²à¦¾à¦‡à¦¨ à¦¦à§‡à¦–à¦¤à§‡ à¦ªà¦¾à¦¨ à¦¤à¦¬à§‡ à¦à¦° à¦®à¦¾à¦¨à§‡ à¦¹à¦² à¦†à¦ªà¦¨à¦¿ à¦à¦•à¦Ÿà¦¿ SOCKS à¦ªà§à¦°à¦•à§à¦¸à¦¿à¦¤à§‡ à¦¸à¦‚à¦¯à§‹à¦— à¦•à¦°à¦¤à§‡ à¦¬à§à¦¯à¦°à§à¦¥à¥¤ à¦†à¦ªà¦¨à¦¾à¦° à¦¨à§‡à¦Ÿà¦“à¦¯à¦¼à¦¾à¦°à§à¦• à¦¸à§‡à¦Ÿà¦†à¦ªà§‡à¦° à¦œà¦¨à§à¦¯ à¦à¦•à¦Ÿà¦¿ à¦¸à¦•à§à¦¸ à¦ªà§à¦°à¦•à§à¦¸à¦¿ à¦ªà§à¦°à¦¯à¦¼à§‹à¦œà¦¨ à¦¹à¦²à§‡, à¦¦à¦¯à¦¼à¦¾ à¦•à¦°à§‡ à¦¨à¦¿à¦¶à§à¦šà¦¿à¦¤ à¦•à¦°à§à¦¨ à¦¯à§‡ à¦†à¦ªà¦¨à¦¿ à¦†à¦ªà¦¨à¦¾à¦° à¦ªà§à¦°à¦•à§à¦¸à¦¿ à¦¬à¦¿à¦¶à¦¦à¦—à§à¦²à¦¿ à¦¸à¦ à¦¿à¦•à¦à¦¾à¦¬à§‡ à¦²à¦¿à¦–à§‡à¦›à§‡à¦¨à¥¤ à¦¯à¦¦à¦¿ à¦à¦•à¦Ÿà¦¿ à¦¸à¦•à§à¦¸ à¦ªà§à¦°à¦•à§à¦¸à¦¿à¦° à¦ªà§à¦°à¦¯à¦¼à§‹à¦œà¦¨ à¦¨à¦¾ à¦¹à¦¯à¦¼ , à¦…à¦¥à¦¬à¦¾ à¦
 †à¦ªà¦¨à¦¿ à¦¨à¦¿à¦¶à§à¦šà¦¿à¦¤ à¦¨à¦¨, à¦¤à¦¬à§‡ à¦¸à¦•à§à¦¸ à¦ªà§à¦°à¦•à§à¦¸à¦¿ à¦›à¦¾à¦¡à¦¼à¦¾ à¦Ÿà¦° à¦¨à§‡à¦Ÿà¦“à¦¯à¦¼à¦¾à¦°à§à¦•à§‡ à¦¸à¦‚à¦¯à§‹à¦—à§‡à¦° à¦šà§‡à¦·à§à¦Ÿà¦¾ à¦•à¦°à§à¦¨à¥¤ <p><h5>à¦¸à¦¾à¦§à¦¾à¦°à¦£ à¦²à¦— à¦¤à§à¦°à§à¦Ÿà¦¿ # 2: à¦—à¦¾à¦°à§à¦¡ à¦°à¦¿à¦²à§‡ à¦ªà§Œà¦à¦›à¦¤à§‡ à¦ªà¦¾à¦°à§‡ à¦¨à¦¾</h5><p class=\"mb-3\"><pre><code> 11/1/2011 21:11:43 PM .500 [à¦¬à¦¿à¦œà§à¦žà¦ªà§à¦¤à¦¿] 127.0.0.1:9150  à¦à¦° à¦‰à¦ªà¦° à¦¸à¦•à§à¦¸ à¦²à¦¿à¦¸à§‡à¦¨à¦¾à¦° à¦†à¦°à¦®à§à¦ à¦•à¦°à§à¦¨\n11/1/2017 21:11:44 PM.300 [à¦¬à¦¿à¦œà§à¦žà¦ªà§à¦¤à¦¿] à¦¬à§à¦Ÿà¦¸à§à¦Ÿà§à¦°à§à¦¯à¦¾à¦ª 80%: à¦Ÿà¦° à¦¨à§‡à¦Ÿà¦“à¦¯à¦¼à¦¾à¦°à§à¦•à§‡ à¦¸à¦‚à¦¯à§à¦•à§à¦¤ à¦¹à¦šà§à¦›à§‡ 11/1/2011 21:11: 44 PM.300 [à¦“à¦¯à¦¼à¦¾à¦°à§à¦¨] à¦†à¦®à¦¾à¦¦à§‡à¦° à¦ªà¦¥à§‡à¦° à¦¹à¦ª 0 à¦à¦° à¦œà¦¨à§à¦¯ à¦¨à§‹à¦¡ à¦–à§à¦à¦œà§‡ à¦ªà¦¾à¦“à¦¯à¦¼à¦¾ à¦¬à§à¦¯à¦°à§à¦¥ à¦¹à¦¯à¦¼à§‡à¦›à§‡à¥¤ à¦à¦‡ à¦¸à¦¾à¦°à§à¦•à¦¿à¦Ÿà¦Ÿà¦¿ à¦–à¦¾à¦°à¦¿à¦œà¥¤\n11/1/2017 21:11:44 PM.500 [à¦¬à¦¿à¦œà§à¦žà¦ªà§à¦¤à¦
 ¿] à¦¬à§à¦Ÿà¦¸à§à¦Ÿà§à¦°à§à¦¯à¦¾à¦ª 85%: à¦ªà§à¦°à¦¥à¦® à¦¹à¦ª à¦¨à¦¿à¦¯à¦¼à§‡ à¦¹à§à¦¯à¦¾à¦¨à§à¦¡à¦¶à§‡à¦• à¦¸à¦®à§à¦ªà¦¨à§à¦¨ à¦¹à¦¯à¦¼à§‡à¦›à§‡\n11/1/2017 21:11:45 PM300 [à¦“à¦¯à¦¼à¦¾à¦°à§à¦¨] à¦ªà¦¥à§‡à¦° à¦¹à¦ª 0 à¦à¦° à¦œà¦¨à§à¦¯ à¦¨à§‹à¦¡ à¦–à§à¦à¦œà§‡ à¦ªà¦¾à¦“à¦¯à¦¼à¦¾ à¦¬à§à¦¯à¦°à§à¦¥ à¦¹à¦¯à¦¼à§‡à¦›à§‡à¥¤à¦à¦‡ à¦¸à¦¾à¦°à§à¦•à¦¿à¦Ÿà¦Ÿà¦¿ à¦–à¦¾à¦°à¦¿à¦œà¥¤</code></pre></p><p class=\"mb-3\">à¦¯à¦¦à¦¿ à¦†à¦ªà¦¨à¦¿ à¦†à¦ªà¦¨à¦¾à¦° à¦Ÿà¦° â€‹â€‹à¦²à¦—à§‡ à¦à¦°à¦•à¦® à¦²à¦¾à¦‡à¦¨ à¦¦à§‡à¦–à¦¤à§‡ à¦ªà¦¾à¦¨ à¦¤à¦¬à§‡ à¦à¦Ÿà¦¿ à¦†à¦ªà¦¨à¦¾à¦° à¦Ÿà¦° à¦¸à¦¾à¦°à§à¦•à¦¿à¦Ÿà§‡à¦° à¦ªà§à¦°à¦¥à¦® à¦¨à§‹à¦¡à§‡à¦° à¦¸à¦¾à¦¥à§‡ à¦¸à¦‚à¦¯à§‹à¦— à¦•à¦°à¦¤à§‡ à¦¬à§à¦¯à¦°à§à¦¥à¥¤ à¦à¦° à¦®à¦¾à¦¨à§‡ à¦¹à¦² à¦¯à§‡ à¦†à¦ªà¦¨à¦¿ à¦¸à§‡à¦¨à§à¦¸à¦° à¦•à¦°à¦¾ à¦à¦•à¦Ÿà¦¿ à¦¨à§‡à¦Ÿà¦“à¦¯à¦¼à¦¾à¦°à§à¦•à§‡à¦° à¦‰à¦ªà¦° à¦†à¦›à§‡à¦¨à¥¤ à¦¦à¦¯à¦¼à¦¾ à¦•à¦°à§‡ à¦¸à§‡à¦¤à§à¦—à§à¦²à¦¿à¦° à¦¸à¦¾à¦¥à§‡ à¦¸à¦‚à¦¯à§‹à¦— à¦¸à§à¦¥à¦¾à¦ªà¦¨ à¦•à¦°à¦¾à¦° à¦šà§‡à¦·à§à¦Ÿà¦¾ à¦•à¦°à§à¦¨
 , এবং এটি সমস্যার সমাধান করা উচিত।</p><h5> সাধারণ লগ ত্রুটি # 3: TLS হ্যান্ডশেক সম্পূর্ণ করতে ব্যর্থ</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [বিজ্ঞপ্তি] বুটস্ট্র্যাপ 10%: ডিরেক্টরি সার্ভারের সাথে হ্যান্ডশেক সমাপ্ত ।(সম্পন্ন হয়ে গেছে; সম্পন্ন হয়ে গেছে ; গণনা 10; সুপারিশ সতর্কতা; হোস্ট [হোস্ট] xxx.xxx.xxx.xx: xxx-এ)\n13-11 -17 19: 53: 49.300 [ওয়ার্ন] সমস্যা বুটস্ট্র্যাপিং। 10% এ আটকে আছে: ডিরেক্টরি সার্ভারের সাথে হ্যান্ডশেক শেষ হচ্ছে।\n13-11-17
  19: 53: 49.300 [à¦“à¦¯à¦¼à¦¾à¦°à§à¦¨] 10 à¦¸à¦‚à¦¯à§‹à¦— à¦¬à§à¦¯à¦°à§à¦¥ à¦¹à¦¯à¦¼à§‡à¦›à§‡: 13-11- 17 19: 53: 49.300 [à¦“à¦¯à¦¼à¦¾à¦°à§à¦¨] 9 à¦Ÿà¦¿ à¦¸à¦‚à¦¯à§‹à¦—à§‡à¦° à¦®à§ƒà¦¤à§à¦¯à§ à¦˜à¦Ÿà§‡ à¦¸à§à¦Ÿà§‡à¦Ÿ à¦¹à§à¦¯à¦¾à¦¨à§à¦¡à¦¸à§‡à¦•à¦¿à¦‚-à¦ (TLS) à¦à¦¸à¦à¦¸à¦à¦² à¦¸à§à¦Ÿà§‡à¦Ÿ SSLv2 / v3 à¦¹à§à¦¯à¦¾à¦²à§‹ A à¦¸à¦¾à¦°à§à¦à¦¾à¦°à§‡à¦° à¦¹à§à¦¯à¦¾à¦¨à§à¦¡à¦¶à§‡à¦• à¦ªà¦¡à¦¼à§à¦¨ \n13-11-17 19: 53: 49.300 [à¦“à¦¯à¦¼à¦¾à¦°à§à¦¨] à¦¸à§à¦Ÿà§‡à¦Ÿ à¦¸à¦‚à¦¯à§‹à¦—à§‡ 1 à¦Ÿà¦¿ à¦¸à¦‚à¦¯à§‹à¦—à§‡à¦° à¦®à§ƒà¦¤à§à¦¯à§ () à¦à¦¸à¦à¦¸à¦à¦² à¦¸à§à¦Ÿà§‡à¦Ÿ (à¦•à§‹à¦¨ SSL à¦…à¦¬à¦œà§‡à¦•à§à¦Ÿ à¦¨à§Ÿ) </code></pre></p><p class=\"mb-3\">\nà¦¯à¦¦à¦¿ à¦†à¦ªà¦¨à¦¿ à¦†à¦ªà¦¨à¦¾à¦° à¦Ÿà¦° à¦²à¦—à§‡ à¦à¦°à¦•à¦® à¦²à¦¾à¦‡à¦¨ à¦¦à§‡à¦–à¦¤à§‡ à¦ªà¦¾à¦¨, à¦¤à¦¾à¦° à¦®à¦¾à¦¨à§‡ à¦Ÿà¦° à¦¡à¦¿à¦°à§‡à¦•à§à¦Ÿà¦°à§€ à¦•à¦°à§à¦¤à§ƒà¦ªà¦•à§à¦·à§‡à¦° à¦¸à¦™à§à¦—à§‡ TLS à¦¹à§à¦¯à¦¾à¦¨à§à¦¡à¦¶à§‡à¦• à¦¸à¦®à§à¦ªà¦¨à§à¦¨ à¦•à¦°à¦¤à§‡ à¦¬à§à¦¯à¦°à§à¦¥ à¥¤ à¦¬à§à¦°à¦¿à¦œà¦—à§
 à¦²à¦¿ à¦¬à§à¦¯à¦¬à¦¹à¦¾à¦° à¦•à¦°à§‡ à¦¸à¦®à§à¦à¦¬à¦¤ à¦à¦Ÿà¦¿ à¦ à¦¿à¦• à¦¹à¦¬à§‡à¥¤ </p><h5>à¦¸à¦¾à¦§à¦¾à¦°à¦£ à¦²à¦— à¦¤à§à¦°à§à¦Ÿà¦¿ # 4 : à¦•à§à¦²à¦• à¦¸à§à¦•à§</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [à¦¬à¦¿à¦œà§à¦žà¦ªà§à¦¤à¦¿] 127.0.0.1:9150 à¦à¦° à¦‰à¦ªà¦° à¦¸à¦•à§à¦¸ à¦²à¦¿à¦¸à§‡à¦¨à¦¾à¦° à¦†à¦°à¦®à§à¦ à¦•à¦°à§à¦¨\n19.11.2017 00:04:48.000 [à¦¬à¦¿à¦œà§à¦žà¦ªà§à¦¤à¦¿] à¦¬à§à¦Ÿà¦¸à§à¦Ÿà§à¦°à§à¦¯à¦¾à¦ª 5%: à¦¡à¦¾à¦‡à¦°à§‡à¦•à§à¦Ÿà¦°à¦¿ à¦¸à¦¾à¦°à§à¦à¦¾à¦°à§‡ à¦¸à¦‚à¦¯à§à¦•à§à¦¤ à¦¹à¦šà§à¦›à§‡\n19.11.2017 00:04:48.200 [à¦¬à¦¿à¦œà§à¦žà¦ªà§à¦¤à¦¿] à¦¬à§à¦Ÿà¦¸à§à¦Ÿà§à¦°à§à¦¯à¦¾à¦ª 10%: à¦¡à¦¾à¦‡à¦°à§‡à¦•à§à¦Ÿà¦°à¦¿ à¦¸à¦¾à¦°à§à¦à¦¾à¦°à§‡à¦° à¦¸à¦¾à¦¥à§‡ à¦¹à§à¦¯à¦¾à¦¨à§à¦¡à¦¶à§‡à¦• à¦¶à§‡à¦· à¦¹à¦šà§à¦›à§‡\n19.11.2017 00:04:48.800 [à¦“à¦¯à¦¼à¦¾à¦°à§à¦¨] à¦¸à§à¦•à¦¿à¦‰à¦¡ à¦¸à¦®à¦¯à¦¼à§‡à¦° à¦¸à¦¾à¦¥à§‡ à¦—à§ƒà¦¹à§€à¦¤ NETINFO à¦¸à§‡à¦² (OR: xxx.xx.x.xx.xxxx: à¦¹à¦¾à¦¤à§‡à¦°):\nà¦®à¦¨à§‡ à¦¹à¦šà§à¦›à§‡ à¦†à¦®à¦¾à¦¦à§‡à¦°
  ঘড়িটা 1 দিন, 0 ঘন্টা, 1 মিনিট বা পিছনের দিকে চলে গেছে বা তাদেরটি এগিয়ে আছে।\nটর কাজ করার জন্য একটি সঠিক ঘড়ি প্রয়োজন: দয়া করে আপনার সময়, সময়জোন এবং তারিখ সেটিংস চেক করুন। </code></pre></p><p class=\"mb-3\">যদি আপনি আপনার টর লগে এরকম লাইন দেখতে পান তবে আপনার সিস্টেম ঘড়িটি ভুল। অনুগ্রহ করে নিশ্চিত করুন যে আপনার ঘড়ির সঠিক সময় নির্ধারণ করা হয়েছে, সঠিক টাইমজোন সহ। তারপর টর্চ পুনরায় আরম্ভ করুন।</p>"
+    },
+    "censorship-6": {
+	"id": "# সেন্সরশিপ -6",
+	"control": "সেন্সরশিপ -6",
+	"title": "আমি টর ব্রাউজারে সংযোগ করতে পারছি না, আমার নেটওয়ার্ক সেন্সর করা হয়েছে?",
+	"description": "<p class=\"mb-3\">আপনি একটি সেন্সর নেটওয়ার্কে হতে পারেন, এবং তাই আপনার সেতু ব্যবহার করে চেষ্টা করা উচিত। কিছু ব্রিজ টর ব্রাউজার এর মধ্যে নির্মিত হয়, এবং আপনি টর লঞ্চার উইন্ডোতে \"কনফিগার\" (তারপর প্রম্পট অনুসরণ) নির্বাচন করে সেতু ব্যবহার করতে পারেন যা আপনি যখন প্রথমবারের জন্য টর ব্রাউজার খুলেন তখন পপ-আপ হিসেবে আসে। আপনার যদি অন্যান্য সেতুর প্রয়োজন হয়, তাহলে আপনি আমাদের <mark><a href=\"https://br
 idges.torproject.org/\">ব্রিজেস ওয়েবসাইটে </a></mark>তাদের পেতে পারেন। সেতু সম্পর্কে আরও তথ্যের জন্য, <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">টর ব্রাউজার ম্যানুয়াল দেখুন</a></mark>। </p>"
+    }
+
+
+}
diff --git a/bn_IN.json b/bn_IN.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/bn_IN.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/bo.json b/bo.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/bo.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/br.json b/br.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/br.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/brx.json b/brx.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/brx.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/bs.json b/bs.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/bs.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ca.json b/ca.json
new file mode 100644
index 000000000..d9e7e21c5
--- /dev/null
+++ b/ca.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "El nostre lloc Web l'han censurat. Pot el Tor ajudar als usuaris a accedir al nostre web?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "El meu lloc web favorit està blocat a través del Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Com puc baixar el Tor si torproject.org està blocat?",
+	"description": "<p class=\"mb-3\">Si no podeu baixar el Tor a través del nostre <mark><a href=\"https://www.torproject.org\">lloc web</a></mark>, podeu obtindre'n una copia a través del GetTor. El GetTor és un servei que respon automàticament als missatges amb enllaços a la última versió del Tor Browser, hostatjada en una gran varietat d'ubicacions que segurament no estiguin blocades, com ara Dropbox, Google Drive i Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "No puc connectar al Tor. Està la meva xarxa blocada?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Tinc problemes per connectar amb el Tor i desconec el motiu.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "No puc connectar al Tor. Està la meva xarxa blocada?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ceb.json b/ceb.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ceb.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/cs.json b/cs.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/cs.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/csb.json b/csb.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/csb.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/cv.json b/cv.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/cv.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/cy.json b/cy.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/cy.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/da.json b/da.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/da.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/de.json b/de.json
new file mode 100644
index 000000000..a188d9d51
--- /dev/null
+++ b/de.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Unsere Website wird blockiert. Kann Tor Browser den Benutzern helfen, die Website trotzdem zu erreichen?",
+	"description": "<p class=\"mb-3\">Tor Browser kann dabei helfen Menschen Zugang zu deiner Webseite an Orten zu verschaffen, wo diese blockiert wird. In den meisten Fällen genügt es <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> herunterzuladen und mit ihm zur blockierten Seite zu navigieren um Zugang zu erhalten. Für Orte mit aufwändigen Zensurmaßnahmen verfügen wir über einen Satz an Zensurumgehungsoptionen, einschließlich <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">austauschbarer Übertragungsarten</a></mark>. Für weitere Informationen dazu öffne die <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser-Benutzeranleitung</a></mark> im Abschnitt <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">Zensur</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "Meine Lieblingswebsite blockiert die Verbindung über Tor.",
+	"description": "<p class=\"mb-3\">Schade, dass Sie die gewünschte Internetseite nicht besuchen können! Manchmal blockieren Webseiten Tor-Nutzer weil sie den Unterschied zwischen regulären Tor-Nutzern und automatisierten Besuchern nicht erkennen können. Den meisten Erfolg hatten wir indem wir die Webseitenbetreiber direkt kontaktieren um die Blockade aufzuheben. Manchmal hilft dies:<br />\"Hallo! Ich habe versucht Ihre Webseite xyz.com mit dem Tor Browser zu besuchen und habe festgestellt, dass Sie Tor-Nutzern nicht erlauben Ihre Webseite zu besuchen. I bitte Sie diese Entscheidung zu überdenken; Tor wird von Menschen auf der ganzen Welt genutzt um deren Privatsphäre zu beschützen und Zensur zu bekämpfen. Indem Sie Tor-Nutzer blockieren, blockieren Sie auch Nutzer in repressiven Staaten, die ein freies Internet nutzen wollen, Journalisten und Wissenschaftler die sich vor einer Erkennung schützen wollen, Whistleblowers, Aktivisten, und gewöhnliche Menschen die invasives Tra
 cking durch Dritte nicht akzeptieren. Bitte beziehen Sie Stellung für digitale Bürgerrechte und Internetfreiheit, und erlauben Sie Tor-Nutzern den Zugriff auf xyz.com. Vielen Dank\"<br />Im Falle von Banken und anderen sensitiven Webseiten sind auch ortsbasierte Blockaden üblich (wenn eine Bank weiß, dass Sie üblicherweise von einem bestimmen Land aus zugreifen, und plötzlich von einem Exit-Server auf der anderen Seite der Welt zugreifen, könnte Ihre Konto (zeitweilig) gesperrt werden). Wenn Sie einen Onion-Dienst nicht erreichen können, sehen Sie hier nach: <a href=\"http://127.0.0.1:5000/#onionservices-3\">Ich kann X.onion nicht erreichen!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Wie kann ich Tor herunterladen, wenn torproject.org blockiert ist?",
+	"description": "<p class=\"mb-3\">Wenn du Tor über unsere <mark><a href=\"https://www.torproject.org\">Website</a></mark> nicht herunterladen kannst, ist es möglich sich einen alternativen Download-Link von Tor über GetTor zusenden zu lassen. GetTor ist ein Dienst der automatisch auf Nachrichten mit Links zur aktuellsten Version des Tor Browsers antwortet, die an verschiedenen Orten wie Dropbox, Google Drive und GitHub gehostet werden.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "Ich kann mich nicht mit Tor Browser verbinden, ist mein Netzwerk zensiert?",
+	"description": "<p class=\"mb-3\">Du befindest dich möglicherweise in einem zensierten Netzwerk und solltes daher versuchen Brücken zu verwenden. Einige Brücken sind in Tor Browser eingebaut und du kannst sie im Tor Browser-Startfenster, das erscheint, wenn du Tor Browser das erste Mal startest, über \"Konfigurieren\" (und die folgende Dialoge) auswählen. Wenn du andere Brücken benötigst, kannst du diese auf unserer <mark><a href=\"https://bridges.torproject.org/\">Brücken-Website</a></mark> erhalten. Für weitere Informationen über Brücken, lies den Abschnitt in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser-Anleitung</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Ich habe Probleme mich mit Tor zu verbinden und kann die Ursache nicht finden.",
+	"description": "<p class=\"mb-3\">Wenn du Verbindungsprobleme hast, wähle bitte die Option \"Tor-Protokoll in die Zwischenablage kopieren\" aus. Füge dann das Tor-Protokoll in eine Textdatei oder ein anderes Dokument ein. Du solltest nun einen der folgenden verbreiteten Fehlereinträge sehen (suche nach foldenden Zeilen in deinem Tor-Protokoll):</p><h5>Üblicher Fehlereintrag #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "Ich kann mich nicht mit Tor Browser verbinden, ist mein Netzwerk zensiert?",
+	"description": "<p class=\"mb-3\">Du befindest dich möglicherweise in einem zensierten Netzwerk und solltes daher versuchen Brücken zu verwenden. Einige Brücken sind in Tor Browser eingebaut und du kannst sie im Tor Browser-Startfenster, das erscheint, wenn du Tor Browser das erste Mal startest, über \"Konfigurieren\" (und die folgende Dialoge) auswählen. Wenn du andere Brücken benötigst, kannst du diese auf unserer <mark><a href=\"https://bridges.torproject.org/\">Brücken-Website</a></mark> erhalten. Für weitere Informationen über Brücken, lies den Abschnitt in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser-Anleitung</a></mark>.</p>"
+    }
+
+
+}
diff --git a/dz.json b/dz.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/dz.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/el.json b/el.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/el.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/en_GB.json b/en_GB.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/en_GB.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/eo.json b/eo.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/eo.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/es.json b/es.json
new file mode 100644
index 000000000..dc9ef431e
--- /dev/null
+++ b/es.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Nuestro sitio web está bloqueado por un censor. ¿El Navegador Tor puede ayudar a los usuarios a acceder a nuestro sitio web?",
+	"description": "<p class=\\\"mb-3\\\">El Navegador Tor ciertamente puede ayudar a que la gente acceda a tu sitio web desde lugares donde está bloqueado. La mayoría de las veces se logrará el acceso simplemente descargando el Navegador Tor y luego usándolo para navegar hacia el sitio bloqueado. En lugares donde hay una fuerte censura, tenemos distintas opciones de elusión disponibles, incluyendo transportes intercambiables. Para más información, por favor lee la sección sobre elusión de la censura del Manual de Usuario del Navegador Tor.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "Mi sitio web favorito está bloqueando el acceso a través de Tor.",
+	"description": "<p class=\"mb-3\">¡Sentimos oír que no puede visitar el sitio web que quería! A veces los sitios web bloquearán a los usuarios de Tor porque no puede diferenciar entre el usuario corriente de Tor y el tráfico automatizado. El mayor éxito que hemos tenido en lograr que los sitios desbloqueen a los usuarios de Tor es hacer que los usuarios contacten con los administradores del sitio directamente. Algo como esto podría funcionar:<br />\"¡Hola! Traté de acceder a su sitio xyz.com mientras usaba el Navegador Tor, y descubrí que no permite que los usarios de Tor accedan a su sitio. Le insto a reconsiderar esta decisión; Tor es usado por personas por todo el mundo para proteger su privacidad y luchar contra la censura. Al bloquear a los usuarios de Tor, probablemente está bloqueando a personas en países represivos que quieren usar una Internet libre, periodistas e investigadores que quieren protegerse a si mismos de ser identificados, informantes, activistas, 
 y gente ordinaria que quiere optar por evitar el rastreo invasivo de terceros. Por favor, adopte una postura fuerte en favor de la privacidad digital y la libertad en Internet, y permita a los usuarios de Tor acceder a xyz.com. Gracias.\"<br />Probablemente pueda evitar barreras idiomáticas si lo hace en inglés:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital privacy and internet freedom, and allow Tor users access to xyz.com. Thank you.\
 "<br />En el caso de bancos, y otros sitios web sensibles, también es común ver bloqueos en base a la ubicación geográfica (si un banco sabe que generalmente accede a sus servicios desde un país, y de repente está conectando desde un repetidor de salida de Tor en la otra parte del mundo, su cuenta puede ser bloqueada o suspendida). Si no puede conectar a un servicio onion, por favor, vea <a href=\"http://127.0.0.1:5000/#onionservices-3\">¡No puedo alcanzar X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "¿Cómo descargo Tor si torproject.org está bloqueada?",
+	"description": "<p class=\"mb-3\">Si no puedes descargar Tor a través de nuestro <mark><a href=\"https://www.torproject.org\">sitio web</a></mark>, puedes obtener una copia de Tor que se te entregará vía GetTor. GetTor es un servicio que responde automáticamente a los mensajes con enlaces a la versión más reciente del Navegador Tor, alojada en distintas ubicaciones, que es menos probable que estén censuradas, como Dropbox, Google Drive, y GitHub.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "No puedo conectar al Navegador Tor, ¿está censurada mi red?",
+	"description": "<p class=\"mb-3\">Podrías estar en una red censurada, así que deberías intentar usar puentes. Algunos puentes van incorporados al Navegador Tor, y puedes usar esos puentes seleccionando \"configurar\" (y luego siguiendo las instrucciones) en la ventana del Arranque de Tor que aparece cuando abres el Navegador Tor por primera vez. Si necesitas otros puentes, puedes obtenerlos en nuestro <mark><a href=\"https://bridges.torproject.org/\">sitio web de puentes</a></mark>. Para más información acerca de los puentes, lee el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">manual del Navegador Tor</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Estoy teniendo problemas conectando a Tor, y no logro averiguar qué es lo que está mal.",
+	"description": "<p class=\"mb-3\"><p class=\"mb-3\">Si está teniendo problemas para conectar, por favor seleccione la opción para \“copiar registro de Tor al portapapeles\”. Luego pegue el registro de Tor en un fichero de texto u otro documento. Debería ver uno de estos errores comunes de registro (busque las siguientes líneas en su registro de Tor):</p><h5>Error común de registro nº 1: Fallo de conexión proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WA
 RN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si ve líneas como estas en su registro de Tor, significa que no está pudiendo conectar a un proxy SOCKS. Si se requiere un proxy SOCKS para la configuración de su red, entonces, por favor, asegúrese de que ha introducido los detalles de su proxy correctamente. Si no se requiere un proxy SOCKS o no está seguro, por favor, trate de conectar a la red Tor sin un proxy SOCKS.<p><h5>Error común de registro nº 2: No se puede conectar a los repetidores guardián</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/20
 17 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si ve líneas como estas en su registro de Tor, significa que su Tor no pudo conectar al primer nodo en el circuito Tor. Esto podría significar que se encuentra en una red que está censurada. Por favor, trate de conectar con puentes, y eso debería corregir el problema.</p><h5>Error común de registro nº 3: No se pudo completar la negociación TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 1
 3-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Si vé líneas como estas en su registro de Tor, significa que Tor no pudo completar una negociación TLS con las autoridades de directorio. Usar puentes probablemente corregirá esto.</p><h5>Error común de registro nº 4: Desfase de reloj</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Si ve líneas com
 o esta en su registro de Tor, significa que su reloj de sistema no está ajustado correctamente. Por favor, asegúrese de que su reloj está ajustado de forma precisa, incluyendo la zona horaria correcta. Luego reinicie Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "No puedo conectar al Navegador Tor, ¿está censurada mi red?",
+	"description": "<p class=\"mb-3\">Podría estar en una red censurada, y por tanto debería intentar usar puentes. Algunos puentes están integrados en el Navegador Tor, y puede usarlos seleccionando \"configurar"\ (y siguiendo las instrucciones) en la ventana del Arranque de Tor que aparece cuando abre  el Navegador Tor por primera vez. Si necesita otros puentes, puede obtenerlos en nuestro <mark><a href=\"https://bridges.torproject.org/\">sitio web de puentes</a></mark>. Para más información sobre los puentes, vea el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\">Manual del Navegador Tor</a></mark>.</p>"
+    }
+
+
+}
diff --git a/es_AR.json b/es_AR.json
new file mode 100644
index 000000000..faf7fb06b
--- /dev/null
+++ b/es_AR.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censura-1",
+	"control": "censura-1",
+	"title": "Nuestro sitio web esta bloqueado por un censor. ¿Puede Tor Browser ayudar a los usuarios a acceder a nuestra web?",
+	"description": "<p class=\"mb-3\">Tor Browser definitivamente puede ayudar a las personas a acceder a su sitio web en lugares donde esté bloqueado. La mayor parte del tiempo, alcanza con descargar <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> y usarlo para navegar el sitio web bloqueado. En lugares donde la censura es mas fuerte contamos con varias opciones disponibles para evitarla. Incluyendo <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">Pluggable Transport</a></mark>. Para mas información, acudí a la sección sobre <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censura </a></mark> del<mark><a href=\"https://tb-manual.torproject.org/en-US/\">Manual de usuario de Tor Browser</a></mark>."
+    },
+    "censorship-2": {
+	"id": "#censura-2",
+	"control": "censura-2",
+	"title": "Mi sitio web bloquea su acceso vía Tor.",
+	"description": "<p class=\"mb-3\">Lamentamos oír que no puedas visitar el sitio web que querés! Aveces algunos sitios web bloquean a los usuarios de Tor pero que no pueden diferenciarlos del trafico generado automáticamente. Tuvimos éxito mayormente pidiendo a los usuarios de Tor que contacten con el administrador del sitio  y le pidan que les permita navegar. Un mensaje como este puede ayudar: <br />\"¡Hola!, traté de acceder al sitio xyz.com usando Tor Browser y me di cuenta que no se lo permiten a usuarios de Tor. Te pido que reconsideres esta decisión; Tor es usado por personas de toda Internet para proteger su privacidad y luchar contra la censura. Bloqueandonos, estas impidiendo que personas en países represivos que quieren usar libremente Internet, periodistas e investigadores que quieren protegerse de ser descubiertos, informantes, activistas y personas ordinarias quienes optan por evitar el rastreo intrusivo de servicios de terceros. Por favor tomá una posición a
  favor de la privacidad digital y la libertad en Internet y permití a los usuarios de Tor acceder a xyz.com, Muchas gracias.\"<br /> En el caso de bancos y otros sitios web sensibles, es común ver bloqueos basados en la ubicacion geográfica (si un banco sabe que generalmente accedes sus servicios desde un pais particular, y de repente te conectas desde un nodo de salida desde el otro lado del mundo, tu cuenta puede ser bloqueada o sospendida). Si no te es posible conectarte a un servicio onion, por favor lee <a href=\"http://127.0.0.1:5000/#onionservices-3\">no puedo conectarme a X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censura-3",
+	"control": "censura-3",
+	"title": "¿Como descargo Tor si torproject.org esta bloqueado?",
+	"description": "<p class=\"mb-3\">Si no podes descargar Tor mediante nuestro <mark><a href=\"https://www.torproject.org\">sitio web</a></mark>, te podemos enviar una copia mediante GetTor. GetTor es un servicio que automáticamente responde mensajes con enlaces a la ultima versión de Tor Browser, alojadas en varios lugares que generalmente no están bloqueados, como Dropbox, Google Drive y Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/es_CL.json b/es_CL.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/es_CL.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/es_CO.json b/es_CO.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/es_CO.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/es_MX.json b/es_MX.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/es_MX.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/et.json b/et.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/et.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/eu.json b/eu.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/eu.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/fa.json b/fa.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/fa.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/fi.json b/fi.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/fi.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/fil.json b/fil.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/fil.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/fo.json b/fo.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/fo.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/fr.json b/fr.json
new file mode 100644
index 000000000..8114facd9
--- /dev/null
+++ b/fr.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censure-1",
+	"control": "censure-1",
+	"title": "Notre site Web est bloqué par un censeur. Le navigateur Tor peut-il aider les utilisateurs à accéder à notre site Web ?",
+	"description": "<p class=\"mb-3\">Le navigateur Tor peut certainement aider les utilisateurs à accéder à votre site Web où il est bloqué. La plupart du temps, il suffira de télécharger le <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">navigateur Tor</a></mark>et de l’utiliser pour naviguer vers le site bloqué pour y accéder. Pour les endroits soumis à une censure forte, de nombreuses options de contournement sont offertes, dont les <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">transports enfichables</a></mark>. Pour de plus amples renseignements, veuillez consulter la rubrique sur la <mark><a href=\"https://tb-manual.torproject.org/fr/circumvention.html\">censure</a></mark> du <mark><a href=\"https://tb-manual.torproject.org/fr/\">guide d’utilisation du navigateur Tor</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censure-2",
+	"control": "censure-2",
+	"title": "Mon site Web préféré bloque l’accès à partir de Tor.",
+	"description": "<p class=\"mb-3\">Nous sommes désolés d’apprendre que vous ne pouvez pas visiter le site Web que vous souhaitez ! Un site Web bloquera parfois les utilisateurs de Tor parce qu’ils ne peuvent pas faire la différence entre l’utilisateur de Tor moyen et le trafic automatisé. Les meilleurs résultats pour débloquer l’accès des utilisateurs de Tor à un site donné ont été obtenus en demandant aux utilisateurs de contacter directement les administrateurs dudit site. Ce qui suit pourrait suffire :<br />« Bonjour ! J’ai essayé d’accéder à votre site xyz.com tout en utilisant le navigateur Tor et j’ai découvert que vous ne permettez pas aux utilisateurs de Tor d’y accéder. Je vous demande instamment de reconsidérer votre décision ; Tor est utilisé partout dans le monde par des personnes souhaitant protéger leurs renseignements personnels tout en combattant la censure. En bloquant les utilisateurs de Tor, vous bloquez vraisemblableme
 nt des personnes se trouvant dans des pays où règne la répression et qui souhaitent utiliser un Internet libre, des journalistes et des chercheurs qui ne veulent pas être découverts, des lanceurs d’alerte, des activistes et des personnes ordinaires qui ne veulent pas être suivies à la trace par des tiers invasifs. Veuillez adopter une position ferme privilégiant la confidentialité numérique et la liberté sur Internet, et permettre aussi aux utilisateurs de Tor d’accéder à xyz.com. Merci.<br />Voici le même message en anglais : <br />“Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from di
 scovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital privacy and internet freedom, and allow Tor users access to xyz.com. Thank you.”<br />Dans le cas de banques ou autres sites Web délicats, il est aussi habituel de constater un blocage d’après la position géographique (si une banque sait que vous accédez habituellement à ses services à partir d’un pays et que vous vous connectez soudainement à partir d’un relais de sortie situé de l’autre côté de la planète, votre compte pourrait être verrouillé ou suspendu). Si vous ne pouvez pas vous connecter à un service oignon, veuillez consulter <a href=“http://127.0.0.1:5000/#onionservices-3”>Je ne peux pas accéder à X.onion !</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censure-3",
+	"control": "censure-3",
+	"title": "Comment puis-je télécharger Tor si torproject.org est bloqué ?",
+	"description": "<p class=\"mb-3\">Si vous ne pouvez pas télécharger Tor à partir de notre <mark><a href=\"https://www.torproject.org\">site Web</a></mark>, une exemplaire de Tor peut vous être livré par GetTor. GetTor est un service qui répond automatiquement aux messages en incluant des liens vers la dernière version du navigateur Tor, hébergée en divers endroits tels que Dropbox, Google Disque et GitHub.</p>"
+    },
+    "censorship-4": {
+	"id": "#censure-4",
+	"control": "censure-4",
+	"title": "Je n'arrive pas à me connecter au navigateur Tor, mon réseau est-il censuré ?",
+	"description": "<p class=\"mb-3\">Il se peut que vous soyez sur un réseau censuré et que vous deviez tenter d’utiliser des ponts. Des ponts sont intégrés au navigateur Tor et vous pouvez utiliser ces ponts en choisissant « Configurer » (puis en suivant les indications) dans la fenêtre du lanceur Tor qui surgit quand vous ouvrez le navigateur Tor pour la première fois. S’il vous faut d’autres ponts, vous pouvez en obtenir sur notre <mark><a href=\"https://bridges.torproject.org/\">site Web BridgeDB</a></mark>. Pour de plus amples renseignements concernant les ponts, consulter le <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">guide d’utilisation du navigateur Tor</a></mark>.</p>\n"
+    },
+    "censorship-5": {
+	"id": "#censure-5",
+	"control": "censure-5",
+	"title": "J’éprouve des difficultés à me connecter à Tor et je n’arrive pas à comprendre ce qui ne va pas.",
+	"description": "<p class=\"mb-3\">Si vous éprouvez des difficultés à vous connecter, veuillez sélectionner l’option « Copier le journal de Tor dans le presse-papiers ». Collez ensuite le journal de Tor dans un fichier texte ou un autre document. Vous devriez trouver l’une de ces erreurs de journal habituelles (cherchez les lignes suivantes dans votre journal de Tor) : </p><h5>Erreur habituelle de journal no 1 : échec de connexion au mandataire</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n
 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous n’arrivez pas à vous connecter à un mandataire SOCKS. Si un mandataire SOCKS est nécessaire à la configuration de réseau, veuillez alors vous assurer d’avoir bien saisi les renseignements concernant le mandataire. Si un mandataire SOCKS n’est pas nécessaire ou si vous ne savez pas, veuillez tenter de vous connecter au réseau Tor sans mandataire SOCKS.<p><h5>Erreur habituelle de journal no 2 : impossible d’atteindre les relais gardes</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/
 2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous n’arrivez pas à vous connecter au premier nœud du circuit Tor. Cela pourrait signifier que vous êtes sur un réseau qui est censuré. Tentez de vous connecter avec des ponts, ce qui devrait corriger la situation.</p><h5>Erreur habituelle de journal no 3 : échec d’établissement d’une liaison TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19
 :53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que Tor n'a pas réussi à établir une liaison TLS avec les autorités d'annuaire. L’utilisation de ponts corrigera certainement cette situation.</p><h5>Erreur habituelle de journal no 4 : décalage d’horloge</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or t
 hat theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">\nSi vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que votre horloge système n’est pas juste. Veuillez vous assurer que votre horloge est réglée avec précision, fuseau horaire inclus, puis redémarrez Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censure-6",
+	"control": "censure-6",
+	"title": "Je n'arrive pas à me connecter au navigateur Tor, mon réseau est-il censuré ?",
+	"description": "<p class=\"mb-3\">Il se peut que vous soyez sur un réseau censuré et que vous deviez tenter d’utiliser des ponts. Des ponts sont intégrés au navigateur Tor et vous pouvez utiliser ces ponts en choisissant « Configurer » (puis en suivant les indications) dans la fenêtre du lanceur Tor qui surgit quand vous ouvrez le navigateur Tor pour la première fois. S’il vous faut d’autres ponts, vous pouvez en obtenir sur notre <mark><a href=\"https://bridges.torproject.org/\">site Web BridgeDB</a></mark>. Pour de plus amples renseignements concernant les ponts, consulter le <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\">guide d’utilisation du navigateur Tor</a></mark>.</p>"
+    }
+
+
+}
diff --git a/fr_CA.json b/fr_CA.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/fr_CA.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/fur.json b/fur.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/fur.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/fy.json b/fy.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/fy.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ga.json b/ga.json
new file mode 100644
index 000000000..4d858b9e9
--- /dev/null
+++ b/ga.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Rinneadh cinsireacht ar ár suíomh Gréasáin. An féidir le húsáideoirí Brabhsálaí Tor a úsáid chun teacht air?",
+	"description": "<p class=\"mb-3\">Cinnte is féidir le daoine Brabhsálaí Tor a úsáid chun teacht ar do shuímh ó áiteanna ina bhfuil cosc air. Go hiondúil, is leor <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Brabhsálaí Tor</a></mark> a íoslódáil agus a úsáid agus beidh daoine in ann do shuíomh a shroicheadh. Chomh maith leis sin, cuirimid uirlisí eile ar fáil a chabhraíonn le daoine in áiteanna faoi chinsireacht throm an córas cinsireachta a sheachaint, mar shampla <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">córais iompair ionphlugáilte</a></mark>. Féach ar <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Lámhleabhar Bhrabhsálaí Tor</a></mark>, go háirithe an t-alt maidir <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">cinsireacht</a></mark> chun tuilleadh eolais a fháil.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "Cuireann an suíomh is ansa liom cosc ar líonra Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Conas is féidir Tor a íoslódáil má tá cosc ar torproject.org?",
+	"description": "<p class=\"mb-3\">Mura bhfuil tú in ann Tor a íoslódáil ónár <mark><a href=\"https://www.torproject.org\">suíomh Gréasáin</a></mark>, is féidir leat Tor a fháil trí sheirbhís GetTor. Is éard atá ann ná seirbhís a thugann freagra ar theachtaireachtaí le nascanna leis an leagan is déanaí de Bhrabhsálaí Tor, óstáilte in áiteanna nach ndéantar cinsireacht orthu rómhinic, mar shampla Dropbox, Google Drive, nó Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "Ní féidir liom ceangal le Brabhsálaí Tor. An bhfuil mo líonra faoi chinsireacht?",
+	"description": "<p class=\"mb-3\">B'fhéidir go bhfuil do líonra faoi chinsireacht. Mar sin, ba chóir duit triail a bhaint as droichead. Tá roinnt droichead ionsuite i mBrabhsálaí Tor, agus is féidir leat iad siúd a úsáid trí \"Cumraigh\" a roghnú (agus na treoracha a leanúint) sa bhfuinneog Tor Launcher a osclaíonn an chéad uair a úsáideann tú Brabhsálaí Tor. Má theastaíonn droichid eile uait, tá siad ar fáil ónár suíomh <mark><a href=\"https://bridges.torproject.org/\">Droichid</a></mark>. Féach ar <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">lámhleabhar Bhrabhsálaí Tor</a></mark> le tuilleadh eolais a fháil.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Ní féidir liom ceangal le líonra Tor, agus ní thuigim cad é an fhadhb.",
+	"description": "<p class=\"mb-3\">Má tá fadhb agat ag ceangal le líonra Tor, úsáid an rogha “cóipeáil logchomhad Tor go dtí an ghearrthaisce.” Ansin, greamaigh an logchomhad i dtéacschomhad nó cáipéis eile. Is dócha go bhfeicfidh tú ceann de na hearráidí coitianta seo (cuardaigh na línte seo a leanas sa logchomhad):</p><h5>Earráid choitianta #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to co
 nnect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Má fheiceann tú na línte seo i do logchomhad Tor, ciallaíonn siad gur theip ort ceangal a bhunú le seachfhreastalaí SOCKS. Má theastaíonn seachfhreastalaí SOCKS uait ar do líonra, deimhnigh gur chuir tú mionsonraí an fhreastalaí isteach go ceart. Mura dteastaíonn seachfhreastalaí SOCKS uair, nó mura bhfuil tú cinnte, déan iarracht ceangal a bhunú le líonra Tor gan seachfhreastalaí SOCKS.<p><h5>Earráid choitianta #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] F
 ailed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Má fheiceann tú na línte seo i do logchomhad Tor, ciallaíonn sé gur theip ort ceangal a bhunú leis an chéad nód sa gciorcad Tor. Uaireanta, ciallaíonn seo go bhfuil do líonra faoi chinsireacht. Bain triail as ceangal trí dhroichead; is dócha go réiteoidh sin an fhadhb.</p><h5>Earráid choitianta #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 co
 nnections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Má fheiceann tú na línte seo i do logchomhad Tor, ciallaíonn sé gur theip ar Tor croitheadh láimhe TLS leis na húdaráis a chur i gcrích. Is dócha go réiteoidh droichead an fhadhb seo.</p><h5>Earráid choitianta #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Má fheiceann tú na línte seo i do logchomhad Tor, c
 iallaíonn sé go bhfuil an clog i do ríomhaire mícheart. Ba chóir duit socruithe an chloig a dheimhniú, an t-am, dáta, agus crios ama san áireamh. Ansin, atosaigh Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "Ní féidir liom ceangal le Brabhsálaí Tor. An bhfuil mo líonra faoi chinsireacht?",
+	"description": "<p class=\"mb-3\">B'fhéidir go bhfuil do líonra faoi chinsireacht. Mar sin, ba chóir duit triail a bhaint as droichead. Tá roinnt droichead ionsuite i mBrabhsálaí Tor, agus is féidir leat iad siúd a úsáid trí \"Cumraigh\" a roghnú (agus na treoracha a leanúint) sa bhfuinneog Tor Launcher a osclaíonn an chéad uair a úsáideann tú Brabhsálaí Tor. Má theastaíonn droichid eile uait, tá siad ar fáil ónár suíomh <mark><a href=\"https://bridges.torproject.org/\">Droichid</a></mark>. Féach ar <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">lámhleabhar Bhrabhsálaí Tor</a></mark> le tuilleadh eolais a fháil.</p>"
+    }
+
+
+}
diff --git a/gd.json b/gd.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/gd.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/gl.json b/gl.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/gl.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/gu.json b/gu.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/gu.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/gu_IN.json b/gu_IN.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/gu_IN.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/gun.json b/gun.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/gun.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ha.json b/ha.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ha.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/he.json b/he.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/he.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/hi.json b/hi.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/hi.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/hr.json b/hr.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/hr.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/hr_HR.json b/hr_HR.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/hr_HR.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ht.json b/ht.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ht.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/hu.json b/hu.json
new file mode 100644
index 000000000..2baffb8b4
--- /dev/null
+++ b/hu.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "A weboldalunkat blokkolta egy cenzor. Hogyan segíti a Tor Böngésző a felhasználókat az oldalunk elérésében?",
+	"description": "<p class=\"mb-3\">A Tor Böngésző segíthet elérni weboldalát, olyan helyekről, ahol azok blokkoltak. A legtöbb esetben elég a  <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Böngésző</a></mark> letöltése és használata a blokkolt oldal megnyitására lehetővé teszi a hozzáférést. Olyan helyeken, ahol a cenzorálás erős, több megkerülő opció elérhető, beleértve a <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">csatolható átviteleket</a></mark> is. További információkért tekintese meg a <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Böngésző Felhasználói kézikönyv</a></mark>  <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">cenzorálásról</a></mark> szóló fejezetét.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "A kedvenc oldalam blokkolja a Tor-on keresztüli hozzáférést.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/hy.json b/hy.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/hy.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ia.json b/ia.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ia.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/id.json b/id.json
new file mode 100644
index 000000000..55c318a59
--- /dev/null
+++ b/id.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Situs kami diblokir sensor. Apakah Tor Browser dapat membantu pengguna kami dalam mengakses situs kami?",
+	"description": "<p class=\"mb-3\">Tor Browser dapat membantu dalam akses situs web Anda dari tempat yang terblokir. Umumnya hanya unduh <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser </a></mark>dan gunakannya untuk membuka akses situs yang terblokir. Di tempat-tempat yang mengalami sensor berat, tersedia beberapa pilihan yang mengatasinya, termasuk <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transport </a></mark>. Untuk info lebih lanjut, silakan baca bagian <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser Manual </a></mark>di bagian <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "Situs web favorit saya memblokir akses melalui Tor.",
+	"description": "<p class=\"mb-3\">Kami turut prihatin atas Anda tidak dapat melakukan akses ke situs web yang Anda inginkan! Kadang beberapa situs web memblokir pengguna Tor karena tidak dapat membedakan pengguna Tor biasa dan lalu-lintas otomatos. Hal terbaik yang dapat dilakukan adalah pengguna menghubungi langsung admin situsnya. Ini mungkin dapat menjadi contoh: <br />\"Halo! Saya berusaha melakukan akses terhadap situs xyz.com Anda melalui Tor Browser dan ternyata Anda tidak mengizinkan pengguna Tor untuk melakukan akses terhadap situs Anda. Saya mohon dengan sangat untuk mempertimbangkan hal ini; Tor digunakan orang-orang di seluruh dunia untuk melindungi privasi mereka dan melawan sensor. Dengan memblokir pengguna Tor, Anda akan memblokir orang-orang di negara-negara represif yang ingin menggunakan Internet secara bebas, wartawan, dan peneliti yang ingin melindungi diri sendiri dari penemuan, termasuk whistleblower, aktivis, dan orang-orang biasa yang ingin terbebas dari pel
 acakan menyeluruh yang dilakukan pihak lain. Mohon dukungan penuh terhadap privasi digital dan kebebasan Internet, dan  izinkan pengguna Tor untuk melakukan akses ke xyz.com. Terima kasih.\"<br />Untuk situs web perbankan dan situs web lain yang sensitif, umumnya ada pemblokiran berdasarkan wilayah geografis (jika bank Anda mengetahui Anda biasanya melakukan akses terhadap jasa mereka dari suatu negara dan jika tiba-tiba Anda membuka situs web mereka dari exit relay di negara lain, akun Anda mungkin akan dikunci atau dibekukan). Jika Anda tidak dapat terhubung ke sebuah onion service, silakan lihat <a href=\"http://127.0.0.1:5000/#onionservices-3\">Saya tidak dapat menghubungi X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Bagaimana cara mengunduh Tor jika torproject.org diblokir?",
+	"description": "<p class=\"mb-3\">Jika Anda tidak dapat mengunduh Tor dari <mark><a href=\"https://www.torproject.org\">situs kami</a></mark>, Tor dapat dikirim kepada Anda melalui GetTor. GetTor adalah service yang yang otomatis merespon pesan berisi tautan ke versi terakhir Tor Browser, yang dihosting di lokasi beragam sehingga kemungkinan kecil disensor, seperti Dropbox, Google Drive, dan Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "Saya tidak bisa terhubung ke Tor Browser, apakah jaringan saya terkena sensor?",
+	"description": "<p class=\"mb-3\">Anda mungkin berada di jaringan yang terdampak sensor, sehingga Anda seharusnya menggunakan bridge yang terintegrasi di Tor Browser. Anda dapat menggunakannya dengan memilih \"configure\" (lalu setelah beberapa pemberitahuan) di jendela launcher Tor yang muncul setelah Anda menjalankan Tor Browser. Jika Anda memerlukan bridge lain, Anda dapat memperolehnya di <mark><a href=\"https://bridges.torproject.org/\">situs web bridge kami </a></mark>. Untuk info lebih lanjut tentang bridge, silakan baca <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser </a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.",
+	"description": "<p class=\"mb-3\">Jika Anda mendapat masalah dalam terhubung ke Jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Jaringan Tor \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Tor gagal ter
 sambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk masalah ini.<
 /p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "Saya tidak bisa terhubung ke Tor Browser, apakah jaringan saya terkena sensor?",
+	"description": "<p class=\"mb-3\">Anda mungkin berada di jaringan yang terdampak sensor, sehingga Anda seharusnya menggunakan bridge yang terintegrasi di Tor Browser. Anda dapat menggunakannya dengan memilih \"configure\" (lalu setelah beberapa pemberitahuan) di jendela launcher Tor yang muncul setelah Anda buka Tor Browser. Jika Anda memerlukan bridge lain, Anda dapat memperolehnya di <mark><a href=\"https://bridges.torproject.org/\">situs web bridge kami </a></mark>. Untuk info lebih lanjut tentang bridge, silakan baca <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">petunjuk Tor Browser </a></mark>.</p>"
+    }
+
+
+}
diff --git a/is.json b/is.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/is.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/it.json b/it.json
new file mode 100644
index 000000000..4858178bd
--- /dev/null
+++ b/it.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censura-1",
+	"control": "censura-1",
+	"title": "Il nostro sito viene censurato da qualcuno. Tor Browser può aiutare gli utenti ad accedervi?",
+	"description": "<p class=\"mb-3\">Il Browser Tor può sicuramente aiutare le persone ad accedere al tuo sito web in luoghi dove è bloccato. La maggior parte delle volte, scaricare semplicemente il <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Browser Tor </a></mark> e usarlo per navigare sul sito bloccato permetterà l'accesso. In luoghi dove è presente un'alta forma di censura, abbiamo un numero di opzioni per aggirarla, includendo <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">una tecnologia per prevenire l'ispezione dei dati </a></mark>. Per ulteriori informazioni, per favore vedi il <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Manuale Utente del Browser Tor</a></mark>nella sezione<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censura</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censura-2",
+	"control": "censura-2",
+	"title": "Il mio sito preferito sta bloccando l'accesso da Tor.",
+	"description": "<p class=\"mb-3\">Scusa di sentirlo, non puoi visitare il sito di web che volutoti! Talvolta siti di web fermerò utilizzatore di Tor perche non possono dire la differenza tra utilizzatore ordinario di Tor e traffico automatico. Il migliore successo noi abbiamo avuto nel prendendo siti a sbloccare utilizzatore di Tor che direttamente contattare amministratori al utilizzatori. Qualcosa come questo può abilitare di funzione<br />\"Ciao! Ho tirato ad accedere vostro sito xyz.com mentre usando Tor Browser e scoperto che tu non permettere utilizzatore di Tor ad accedere vostro sito. Io spingo te a riconsiderare questo decisione; Tor é usando da uomini sul mondo per difendere loro intimita e censura di lotta. Con bloccare utilizzatore di Tor, sei come bloccando uomini nel paesi repressivi chi vogliono ad usare un rete libero, giornalisti e ricercatori chi vogliono a difendere loro stessi da scoperta, spione, attiviste e uomini ordinari chi vogliono decidere di non parte
 cipare di invasivo controllo terzo. Per piacere prende atteggiamento poderoso per favore di intimata digitale e libero di rete e permette utilizzatore di Tor ad accedere xyz.com. Grazie.\"<br />In caso di bance e altro siti sensitivi, é anche comune a vedere bloccando tratto geografia (se un banca sa tu generalmente accedere loro servizio da una campagna e improvvisamente sei connettendo da un relè uscita sulla altro lato di mondo, tuo conto può chiuso o pensile). Se sei incapace di connettere a servizio di cipolla, per piacere consulta<a href=\"http://127.0.0.1:5000/#onionservices-3\">Non posso accedere X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censura-3",
+	"control": "censura-3",
+	"title": "Come posso scaricare Tor se torproject.org viene bloccato?",
+	"description": "<p class=\"mb-3\">Se non puoi scaricare Tor dal nostro <mark><a href=\"https://www.torproject.org\">sito</a></mark>, puoi ottenerne una copia attraverso GetTor. GetTor è un servizio che risponde automaticamente a messaggi con link all'ultima versione di Tor Browser, ospitata in vari luoghi che sono difficili da censurare, come Dropbox, Google Drive e GitHub.</p>"
+    },
+    "censorship-4": {
+	"id": "#censura-4",
+	"control": "censura-4",
+	"title": "Non posso connettermi a Tor Browser, la mia rete è censurata?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censura-5",
+	"control": "censura-5",
+	"title": "Sto avendo problemi nella connessione a Tor e non riesco a capire quale sia la causa.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censura-6",
+	"control": "censura-6",
+	"title": "Non posso connettermi a Tor Browser, la mia rete è censurata?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ja.json b/ja.json
new file mode 100644
index 000000000..a8465c9e6
--- /dev/null
+++ b/ja.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#検閲-1",
+	"control": "検閲-1",
+	"title": "私たちのWEBサイトは検閲によりブロックされました。TorブラウザーはユーザーのWEBサイトへのアクセスを助けてくれますか？",
+	"description": "<p class=\"mb-3\">あなたのサイトがブロックされる場合、Torブラウザーが人は確実にアクセスできるよう助ける。大抵の場合、<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Torブラウザー</a></mark>を利用してサイトのアドレスにアクセスするだけで十分です。より厳しい検閲がある場合、<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">Pluggable Transport</a></mark>など様々な迂回方法があります。詳細については、<mark><a href=\"https://tb-manual.torproject.org/en-US/\">Torブラウザーのユーザーマニュアル</a></mark>に<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">検閲</a></mark>に関する章を調べて下さい。</p>"
+    },
+    "censorship-2": {
+	"id": "#検閲-2",
+	"control": "検閲-2",
+	"title": "お気に入りのWEBサイトへのアクセスがTorによりブロックされました。",
+	"description": "<p class=\"mb-3\">あなたの望むサイトにアクセスできないことは申し訳ありません！サイトはしばしばTorユーザーをブロックします。彼らは通常のTorユーザーと自動トラフィックの違いを見分けることができないからです。ブロックを解除しサイトを取得するのにもっとも適した手段は、TOAユーザーがサイト管理者に対して直接的にコンタクトを取ることです。このようなトリックが使えるかもしれません:<br />“やあ！私はあなたのサイトxyz.comにTorブラウザーでアクセスしようとしたのだけれど、あなたのサイトはTorユーザーへのアクセスを許可していないみたいなんだ。この決定は再検討することをお勧めするよ。Torはプライバシー保護と検閲への対抗の為に世界中の人々によって使われているんだ。Torユーザーをブロックする
 ことは、自由なインターネットを望む抑圧的な国の人々や、露出から守られるべきジャーナリストや調査員、内部告発者、活動家、及び侵略的なサードパーティのトラッキングから逃れたい普通の人々をもブロックしてしまうんだ。どうか、デジタルプライバシーとインターネットの自由を尊重して、Torユーザーがxyz.comにアクセスできるようにしてほしい。ありがとう。”<br />銀行やその他の厳密なWEBサイトの場合、その地域の地理的な遮断情報を見ましょう（銀行があなたが普段ある国からアクセスしていることを知っていれば、あなたのアカウントは突然ロックされたり中断される可能性があります）。もしあなたがオニオンサービスに接続できない場合は、<a href=\"http://127.0.0.1:5000/#onionservices-3\">X.onionã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã›ã‚“</a>ã‚’å‚ç…§ã
 —ã¦ãã ã•ã„ã€‚</p>"
+    },
+    "censorship-3": {
+	"id": "#検閲-3",
+	"control": "検閲-3",
+	"title": "torproject.orgがブロックされている場合、どのようにTorをダウンロードできますか？",
+	"description": "<p class=\"mb-3\">私たちの<mark><a href=\"https://www.torproject.org\">WEBサイト</a></a>からTorをダウンロードできない場合、GetTorによってTorをダウンロードできます。GetTor は最新バージョンの Torブラウザー へのリンクをメッセージで自動的に返信するサービスです。ファイルは Dropbox，Google Drive および GitHub といったさまざまな検閲される可能性が低い場所でホストされています。 </p>"
+    },
+    "censorship-4": {
+	"id": "#検閲-4",
+	"control": "検閲-4",
+	"title": "Torブラウザーに接続できません。私のネットワークは検閲されていますか？",
+	"description": "<p class=\"mb-3\">検閲されるネットワークに接続している可能性があるので、ブリッジを使って試してみて下さい。あるブリッジはTorブラウザーに組み込まれるから、初めてTorブラウザーを開く時に表示されるTor Launcherウィンドウにある「設定」を選択して下さい（そしてプロンプトに従って下さい）。他のブリッジが必要なら、私たちの<mark><a href=\"https://bridges.torproject.org/\">ブリッジWEBサイト</a></mark>から手に入れることができます。詳細については、<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Torブラウザーのユーザーマニュアル</a></mark>にブリッジに関する章を調べて下さい。</p>"
+    },
+    "censorship-5": {
+	"id": "#検閲-5",
+	"control": "検閲-5",
+	"title": "Torにアクセスできないが、何が問題なのか分かりません。",
+	"description": "<p class=\"mb-3\">Torにアクセスできない場合、「Torログをクリップボードにコピーする」選択肢を選んで、ログをメモ帳あるいはドキュメントファイルに貼り付けて下さい。以下の良くあるエラーメッセージを見つけるはずです：</p><h5>よくあるログエラー#1: プロキシ接続失敗</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..
 xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Torログにこのような行があれば、SOCKSプロキシと繋がれないということです。ネットワークにはSOCKSプロキシが必要なら、設定を確認して下さい。SOCKSプロキシが必要ではない場合、あるいはよく分からない場合、SOCKSプロキシ無しでTorにアクセスしてみて下さい。<p><h5>よくあるログエラー#2: ガードリレーと接続できない</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discardi
 ng this circuit.</code></pre></p><p class=\"mb-3\">Torログにこのような行があれば、Torはcircuitの最初のノードと接続できなかったということです。検閲されるネットワークに接続している可能性があります。ブリッジを使ってTorにアクセスしたら問題を解決できるはずです。</p><h5>よくあるログエラー#3: TLSハンドシェイクの失敗</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state
  connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Torログにこのような行があれば、TorがディレクトリオーソリティとTLSハンドシェイクを完了できなかったということです。ブリッジを使ってTorにアクセスしたら問題を解決できる可能性がある。</p><h5>よくあるログエラー#4: クロックスキュー</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p clas
 s=\"mb-3\">Torログにこのような行があれば、システム・クロックには間違った時刻が設定されます。システム・クロックを正しい時刻とタイムゾーンに合わせてからTorを再起動して下さい。 </p>"
+    },
+    "censorship-6": {
+	"id": "#検閲-6",
+	"control": "検閲-6",
+	"title": "Torブラウザーに接続できません。私のネットワークは検閲されていますか？",
+	"description": "<p class=\"mb-3\">検閲されるネットワークに接続している可能性があるので、ブリッジを使って試してみて下さい。あるブリッジはTorブラウザーに組み込まれるから、初めてTorブラウザーを開く時に表示されるTor Launcherウィンドウにある「設定」を選択して下さい（そしてプロンプトに従って下さい）。他のブリッジが必要なら、私たちの<mark><a href=\"https://bridges.torproject.org/\">ブリッジWEBサイト</a></mark>から手に入れることができます。詳細については、<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Torブラウザーのユーザーマニュアル</a></mark>にブリッジに関する章を調べて下さい。</p>"
+    }
+
+
+}
diff --git a/jv.json b/jv.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/jv.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ka.json b/ka.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ka.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/kk.json b/kk.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/kk.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/km.json b/km.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/km.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/kn.json b/kn.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/kn.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ko.json b/ko.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ko.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ko_KR.json b/ko_KR.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ko_KR.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ku.json b/ku.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ku.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ku_IQ.json b/ku_IQ.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ku_IQ.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/kw.json b/kw.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/kw.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ky.json b/ky.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ky.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/la.json b/la.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/la.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/lb.json b/lb.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/lb.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/lg.json b/lg.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/lg.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ln.json b/ln.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ln.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/lo.json b/lo.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/lo.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/lt.json b/lt.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/lt.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/lv.json b/lv.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/lv.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/mg.json b/mg.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/mg.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/mi.json b/mi.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/mi.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/mk.json b/mk.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/mk.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ml.json b/ml.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ml.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/mn.json b/mn.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/mn.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/mr.json b/mr.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/mr.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ms_MY.json b/ms_MY.json
new file mode 100644
index 000000000..1e214b28c
--- /dev/null
+++ b/ms_MY.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Laman sesawang kami telah ditapis. Bolehkan Pelayar Tor membantu pengguna capai laman sesawang kami?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Bagaimana saya boleh memuat turun Tor jika torproject.org telah disekat?",
+	"description": "<p class=\"mb-3\">Jika anda tidak boleh memuat turun Tor melalui <mark><a href=\"https://www.torproject.org\">laman sesawang</a></mark> kami, anda boleh dapatkan satu salinan Tor yang dihantar terus menerusi GetTor. GetTor merupakan servis yang membalas secara automatik mesej dengan pautan ke versi terkini Pelayar Tor, telah dihos dengan pada pelbagai lokasi yang berkemungkinan tidak ditapis, seperti Dropbox, Google Drive, dan Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Saya menghadapi masalah ketika menyambung dengan Tor, dan saya tidak tahu apa masalah yang berlaku.",
+	"description": "<p class=\"mb-3\">Jika anda menghadapi masalah sambungan, pilih pilihan \"salin log Tor ke papan keratan.” Kemudian tampal log Tor ke dalam fail teks atau lain-lain fail dokumen. Anda akan dapati terdapat ralat log (lihat baris berikut di dalam log Tor anda):</p><h5>Ralat log umum #1: Kegagalan sambungan proksi</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\"
 )</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud anda gagal menyambung dengan proksi SOCKS. Jika proksi SOCKS diperlukan untuk persediaan rangkaian anda, maka sila pastikan anda telah memasukkan perincian proksi tersebut dengan betul.  Jika proksi SOCKS tidak diperlukan, atau anda tidak pasti,  cuba sambung ke rangkaian Tor tanpa proksi SOCKS.<p><h5>Ralat log umum #2: Tidak dapat capai geganti pengawal</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-
 3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud Tor anda gagal menyambung ke nod pertama dalam litar Tor. Ia bermaksud anda berada dalam rangkaian bertapis. Cuba menyambung dengan titi, dan sepatutnya ia masalah selesai.</p><h5>Ralat log umum #3: Gagal menyelesaikan jabat-tangan TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat ba
 ris seperti ini di dalam log Tor anda, ia bermaksud Tor gagal menyelesaikan jabat-tangan TLS dengan autoriti direktori. Penggunaan titi dapat menyelesaikan masalah ini.</p><h5>Ralat log umum #4: Pencong jam</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini dalam log Tor anda, ia bermaksud jam sistem anda salah. Sila pastikan jam anda telah ditetapkan dengan tepat, termasuklah zon waktu yang betul.
  Kemudian mulakan semula Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/mt.json b/mt.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/mt.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/my.json b/my.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/my.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/nah.json b/nah.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/nah.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/nap.json b/nap.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/nap.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/nb.json b/nb.json
new file mode 100644
index 000000000..80a0c173c
--- /dev/null
+++ b/nb.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Vår nettside er blokkert av en sensurinstans. Kan Tor-nettleseren hjelpe brukere å nå den?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "Min favorittnettside blokkerer tilgang fra Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Hvordan kan jeg laste ned Tor hvis torproject.org er blokkert?",
+	"description": "<p class=\"mb-3\">Hvis du ikke kan laste ned Tor fra vår <mark><a href=\"https://www.torproject.org\">nettside</a></mark>, kan du få en kopi levert via GetTor, en tjeneste som automatisk svarer med lenker til seneste versjon av Tor-nettleseren, hvis vertskap er betjent av forskjellige steder det er mindre mulighet for at er sensurert, som Dropbox, Google Drive og GitHub.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/nds.json b/nds.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/nds.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ne.json b/ne.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ne.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/nl.json b/nl.json
new file mode 100644
index 000000000..9f96969e7
--- /dev/null
+++ b/nl.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censuur-1",
+	"control": "censuur-1",
+	"title": "Onze website wordt geblokkeerd door een censor. Kan Tor Browser gebruikers helpen toegang tot onze website te krijgen?",
+	"description": "<p class=\"mb-3\">Tor Browser kan mensen zeker helpen toegang te krijgen tot uw website op plaatsen waar deze is geblokkeerd. Meestal gewoon downloaden van de <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> en dan gebruik het om te navigeren naar de geblokkeerde site en zal toegang toestaan. Op plaatsen waar sprake is van zware censuur hebben we een aantal opties voor censuurontwijking beschikbaar, waaronder <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">inplugbare transports</a></mark>. Voor meer informatie, zie de <mark><a href=\"https://tb-manual.torproject.org/en-US/\"> Tor Browser Gebruiker Manual</a></mark> hoofdstuk over <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censuur-2",
+	"control": "censuur-2",
+	"title": "Mijn favoriete website blokkeert de toegang via Tor.",
+	"description": "<p class=\"mb-3\">Sorry om te horen dat je de website die je wilde niet kunt bezoeken! Soms blokkeren websites Tor-gebruikers omdat ze niet het verschil kunnen zien tussen de gemiddelde Tor-gebruiker en automatisch verkeer. Het beste succes dat we hebben gehad bij het ontgrendelen van Tor-gebruikers, is ervoor te zorgen dat gebruikers rechtstreeks contact opnemen met de sitebeheerders. Zoiets zou de slag kunnen slaan: <br /> \"Hallo! Ik probeerde toegang tot uw site xyz.com te krijgen tijdens het gebruik van Tor Browser en ontdekte dat u Tor gebruikers geen toegang tot uw site verleent. Ik dring er bij u op aan om deze beslissing opnieuw te overwegen; gebruikt door mensen over de hele wereld om hun privacy te beschermen en censuur te bestrijden. Door Tor-gebruikers te blokkeren, blokkeert u waarschijnlijk mensen in repressieve landen die een gratis internet willen gebruiken, journalisten en onderzoekers die zichzelf willen beschermen tegen ontdekking, klokkenluiders
 , activisten en gewone mensen die willen opteren voor invasieve tracking door derden. Stel u ten stelligste voor ten gunste van digitale privacy en internetvrijheid en geef Tor-gebruikers toegang tot xyz.com. Dank u. \"<br />In het geval van banken en andere gevoelige websites, is het ook gebruikelijk om op geografie gebaseerde blokkering te zien (als een bank weet dat u over het algemeen toegang hebt tot hun services vanuit het ene land en plotseling verbinding maakt via een uitgaande relais aan de andere kant van de wereld, is uw account mogelijk vergrendeld Of geschorst). Als u geen verbinding kunt maken met een onion service, raadpleegt u <a href=\"http://127.0.0.1:5000/#onionservices-3\">Ik kan X.onion niet bereiken! </a></p>"
+    },
+    "censorship-3": {
+	"id": "#censuur-3",
+	"control": "censuur-3",
+	"title": "Hoe kan ik Tor downloaden als het torproject.org is geblokkeerd?",
+	"description": "<p class=\"mb-3\">Als u Tor niet via onze <mark><a href=\"https://www.torproject.org\">website</a></mark> kunt downloaden, kunt u via GetTor een exemplaar van Tor aan u laten bezorgen. GetTor is een service die automatisch reageert op berichten met links naar de nieuwste versie van Tor Browser, gehost op verschillende locaties die minder vaak worden gecensureerd, zoals Dropbox, Google Drive en Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censuur-4",
+	"control": "censuur-4",
+	"title": "Ik kan geen verbinding maken met de Tor-browser, wordt mijn netwerk gecensureerd?",
+	"description": "<p class=\"mb-3\">Mogelijk bevindt u zich op een gecensureerd netwerk en moet u dus proberen bruggen te gebruiken. Sommige bruggen zijn ingebouwd in Tor Browser en u kunt die bruggen gebruiken door \"configure\" te kiezen (gevolgd door de aanwijzingen) in het Tor Launcher-venster dat verschijnt wanneer u Tor Browser voor de eerste keer opent. Als u andere bruggen nodig heeft, kunt u ze vinden op onze <mark><a href=\"https://bridges.torproject.org/\">Bridges-website</a></mark>.Voor meer informatie over bruggen, zie de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser-handleiding</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censuur-5",
+	"control": "censuur-5",
+	"title": "Ik ondervind problemen bij het verbinding maken met Tor, en ik vind maar niet wat er fout gaat.",
+	"description": "<p class=\"mb-3\">Als u problemen ondervindt bij het verbinden, selecteert u de optie om \"Tor log naar klembord te kopiëren\". Plak vervolgens het Tor-log in een tekstbestand of een ander document. U zou een van deze Vaak voorkomend logfouten moeten zien (kijk naar de volgende regels in uw Tor-logboek): </p><h5>Vaak voorkomend logboekfout # 1: Proxy-verbindingsfout</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09: 23: 40.800 [LET OP] Opening Socks luisteraar op 127.0.0.1 : 9150 \n 2017-10-29 09: 23: 47.900 [LET OP] Bootstrapped 5%: verbinden met directoryserver \n 2017-10-29 09: 23: 47.900 [LETICE] Bootstrap 10%: handshake beëindigen met directoryserver \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-clie
 nt: kan toxx..xxx..xxx.xx: xxxxx niet verbinden (\"algemene SOCKS-serverstoring\") </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, is dit betekent dat u geen verbinding kunt maken met een SOCKS-proxy. Als een SOCKS-proxy vereist is voor uw netwerkconfiguratie, moet u ervoor zorgen dat u uw proxy-gegevens correct hebt ingevoerd. Als een SOCKS-proxy niet vereist is, of als u het niet zeker weet, probeer dan verbinding te maken met het Tor-netwerk zonder een SOCKS-proxy.<p><h5>Gebruikslog fout # 2: Kan relais niet bereiken</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM .500 [LET OP] Luisteraar luisterpositie openen op 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [LET OP] Bootstrapped 80%: Verbinding maken met het Tor-netwerk \n 11/1/2017 21:11:44 PM.300 [WARN] Kan knooppunt voor hop 0 van ons pad niet vinden. Dit circuit weggooien. \n 11/1/2017 21:11:44 PM.500 [LET OP] Bootstrap 85%: Handshake beëindigen met eerste hop \n 11/1/2017 21:11:45 P
 M.300 [WARN] Kan knooppunt niet vinden voor hop 0 van ons pad. Dit circuit verwijderen.</code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dit dat uw Tor geen verbinding kon maken met het eerste knooppunt in het Tor-circuit. Dit kan betekenen dat u zich op een netwerk bevindt dat gecensureerd is. Probeer te verbinden met bruggen, en dat zou het probleem moeten verhelpen.</p><h5> Algemene logfout # 3: Kan TLS-handshake niet voltooien</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [LET OP] Bootstrap 10%: handshake beëindigen met directoryserver \n 13-11-17 19: 53: 49.300 [WARN] Probleem met bootstrappen. Vastgelopen met 10%: handshake beëindigen met directoryserver. (GEDAAN, GEDAAN, aantal 10; advieswaarschuwing; host [host] op xxx.xxx.xxx.xx: xxx) \n 13-11-17 19: 53: 49.300 [WARN] 10 verbindingen zijn mislukt: \n 13-11-17 19: 53: 49.300 [WARN] 9 verbindingen stierven in staatshandshaking (TLS) met SSL-status SSLv2 / v3 lezen server
  hallo A in HANDSHAKE \n 13-11-17 19: 53: 49.300 [WARN] 1 verbindingen zijn overleden in state connect () ing met SSL-staat (No SSL-object) </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dat Tor een TLS-handshake niet kon voltooien met de directory-autoriteiten. Het gebruik van bruggen lost dit waarschijnlijk op.</p><h5>Veel logboekfout # 4: Klok skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00: 04: 47.400 [LET OP] Opening Socks luisteraar op 127.0.0.1:9150 \n  19.11.2017 00: 04: 48.000 [LET OP] Bootstrap 5%: verbinding maken met directoryserver \n  19.11.2017 00: 04: 48.200 [LET OP] Bootstrap 10%: handshake beëindigen met directoryserver \n  19.11.2017 00: 04: 48.800 [WARN] NETINFO-cel ontvangen met scheve tijd (OF: xxx.xx.x.xx: xxxx): het lijkt erop dat onze klok 1 dag, 0 uur, 1 minuut achterloopt, of die van hen liggen voor de deur. \n  Tor vereist een nauwkeurige klok om te werken: controleer uw tijd-, tijdzone- en datuminstellin
 gen.</code></pre></p><p class=\"mb-3\">Als u lijnen zoals deze in uw Tor-logboek ziet, betekent dit dat uw systeemklok onjuist is. Zorg ervoor dat uw klok correct is ingesteld, inclusief de juiste tijdzone. Start dan Tor opnieuw. </p>"
+    },
+    "censorship-6": {
+	"id": "#censuur-6",
+	"control": "censuur-6",
+	"title": "Ik kan geen verbinding maken met de Tor-browser, wordt mijn netwerk gecensureerd?",
+	"description": "<p class=\"mb-3\">Mogelijk bevindt u zich op een gecensureerd netwerk en moet u dus proberen bruggen te gebruiken. Sommige bruggen zijn ingebouwd in Tor Browser en u kunt die bruggen gebruiken door \"configure\" te kiezen (gevolgd door de aanwijzingen) in het Tor Launcher-venster dat verschijnt wanneer u Tor Browser voor de eerste keer opent. Als u andere bruggen nodig heeft, kunt u ze vinden op onze <mark><a href=\"https://bridges.torproject.org/\">Bridges-website</a></mark>.Voor meer informatie over bruggen, zie de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Browser-handleiding</a></mark>.</p>"
+    }
+
+
+}
diff --git a/nl_BE.json b/nl_BE.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/nl_BE.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/nn.json b/nn.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/nn.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/nso.json b/nso.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/nso.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/oc.json b/oc.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/oc.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/om.json b/om.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/om.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/or.json b/or.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/or.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/pa.json b/pa.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/pa.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/pap.json b/pap.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/pap.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/pl.json b/pl.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/pl.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/pms.json b/pms.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/pms.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ps.json b/ps.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ps.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/pt.json b/pt.json
new file mode 100644
index 000000000..d50c3aefb
--- /dev/null
+++ b/pt.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "O nosso site da Web está bloqueado por um censor. O Tor Browser pode ajudar os utilizadores a aceder ao nosso site da Web?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "O meu site da Web favorito está a bloquear o acesso ao Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Como é que eu transfiro o Tor se o torproject.org estiver bloqueado?",
+	"description": "<p class=\"mb-3\">Se não conseguir transferir o Tor através do nosso <mark><a href=\"https://www.torproject.org\">site da Web</a></mark>, pode obter uma cópia do Tor enviada para si através do GetTor. O GetTor é um serviço que responde automaticamente às mensagens com hiperligações para a versão mais recente do Tor Browser, alojado em vários locais que são menos propensos a serem censurados, tais como Dropbox, Google Drive e Github.1"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "Eu não consigo ligar ao Tor Browser. A minha rede está censurada?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Eu estou a ter problemas para ligar ao Tor, e eu não consigo descobrir o que está errado.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "Eu não consigo ligar-me ao Tor Browser. A minha rede está censurada?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/pt_BR.json b/pt_BR.json
new file mode 100644
index 000000000..75c340dd5
--- /dev/null
+++ b/pt_BR.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censura-1",
+	"control": "censura-1",
+	"title": "Nosso site está bloqueado por um censor. O Navegador Tor pode ajudar aos usuários a acessar nosso site?",
+	"description": "<p class=\"mb-3\">O Navegador Tor pode certamente ajudar as pessoas a acessarem seu site em lugares onde ele é bloqueado. Na maioria das vezes, basta baixar o<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Navegador Tor</a></mark>  e usá-lo para navegar até o site bloqueado para permitir o acesso. Em locais onde há uma forte censura, temos várias opções de contornar a censura disponíveis, incluindo <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">transportes plugáveis</a></mark>. Para mais informações, consulte o<mark>Manual do Usuário do Navegador Tor</a>sobre censura</mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censura-2",
+	"control": "censura-2",
+	"title": "Meu website favorito está bloqueando o acesso via Tor.",
+	"description": "<p class=\"mb-3\"> Lamentamos saber que você não pode visitar o website que quer! Às vezes, os websites bloqueam os usuários do Tor porque não sabem a diferença entre o usuário médio e o tráfego automatizado. Uma estratégia na qual temos obtido sucesso para fazer os websites desbloquearem os usuários do Tor é fazer com que os próprios usuários contatem os administradores do site diretamente. Algo assim deve funcionar: <br /> \"Olá! Eu tentei acessar seu website xyz.com enquanto utilizando o Tor Browser e descobri que não há permissão de acesso para usuários do Tor. Eu peço que reconsiderem essa decisão; o Tor é utilizado por pessoas de todo o mundo que querem proteger sua privacidade e lutar contra a censura. Ao bloquear os usuários do Tor, vocês estão provavelmente bloqueando pessoas que querem usar uma internet livre em países opressores, jornalistas e pesquisadores que querem se proteger, ativistas e pessoas comuns que querem se livrar d
 o rastreamento de terceiros invasivos. Por favor, tomem uma posição forte em favor da privacidade digital e da liberdade na internet e permitam os usuários do Tor o acesso ao xyz.com. Obrigado.\" <br />No caso dos bancos, e outros sensitive websites, é também comum que apareçam bloqueios baseados na localização geográfica (se um banco sabe que você geralmente acessa seus serviços de um país, e de repente você está conectando de uma exit relay no outro lado do mundo, sua conta pode ser trancada ou suspensa). Se você não consegue se conectar a um onion service, por favor ver <a href=\"http://127.0.0.1:5000/#onionservices-3\">Não consigo acessar X.onion! </a> </p>"
+    },
+    "censorship-3": {
+	"id": "#censura-3",
+	"control": "censura-3",
+	"title": "Como eu baixo Tor caso torproject.org esteja bloqueado?",
+	"description": "<p class=\"mb-3\">Se não conseguir fazer o download usando o <mark><a href=\"https://www.torproject.org\"> website </a></mark>, você pode obter uma cópia do Tor via GetTor. GetTor é um serviço que automaticamente responde às mensagens com links para a última versão do Navegador Tor, hospedado em uma variedade de locais menos propensos a serem censurados, como Dropbox, Google Drive e GitHub. </p>"
+    },
+    "censorship-4": {
+	"id": "#censura-4",
+	"control": "censura-4",
+	"title": "Eu não consigo conectar ao Tor Browser, a minha rede está censurada?",
+	"description": "<p class=\"mb-3\">Você pode estar em uma rede censurada e, assim, você deveria tentar usar bridges. Algumas bridges são construídas no Tor Browser e você pode usá-las escolhendo \"configure\" (e seguir as instruções) na janela Tor Launcher que aparece quando você abre o Tor Browser pela primeira vez. Se você precisar de outras bridges, você pode consegui-las em nosso <mark><a href=\"https://bridges.torproject.org/\">Bridges website </a></mark>. Para mais informações sobre bridges, veja o <a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manual do Tor Browser </a><mark>.</mark>"
+    },
+    "censorship-5": {
+	"id": "#censura-5",
+	"control": "censura-5",
+	"title": "Estou tendo problemas para conectar ao Tor e não consigo descobrir o que está dando errado.",
+	"description": "<p class=\"mb-3\">Se estiver tendo problemas ao se conectar, por favor selecione a opção para \"copiar o log de Tor para a área de transferências\". Em seguida cole o log do Tor em um arquivo de texto ou outro documento. Você deverá ver um destes erros de logs comuns (procure as seguintes linhas no seu log do Tor):<h5>Erro de log comum #1: Falha na conexão de Proxy</h5><p class=\"mb-3\"><pre>2017-10-29 09:23:40.800 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 5%: Conectando ao servidor do diretório\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 10%: Concluindo o 'handshake' com o servidor do diretório\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: não foi possível conectar-se à  xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: não foi possível conectar-se à  xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:0
 8.900 [AVISO] Cliente: de Proxy: não foi possível conectar-se à  xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") Se você encontrar linhas como estas  em seu log do Tor, isto significa que falhou em conectar-se à um SOCKS proxy. Se um SOCKS proxy é obrigatório para a sua configuração de rede, por favor certifique-se que você digitou seus detalhes de proxy corretamente. Se um SOCKS proxy não é obrigatório, ou você não está certo sobre isso, por favor tente conectar-se à rede Tor sem um SOCKS proxy. Erro de log comum #2: Can’t reach guard relays 11/1/2017 21:11:43 PM.500 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [OBSERVE] Bootstrapped 80%: Conectando à rede Tor\n11/1/2017 21:11:44 PM.300 [AVISO] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [OBSERVE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [AVISO] Failed to find node for hop 0 of our 
 path. Discarding this circuit.If you see lines like these in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.Common log error #3: Failed to complete TLS handshake 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)If you see lines like this in your Tor log, it means that Tor failed to complete a TLS hands
 hake with the directory authorities. Using bridges will likely fix this.Common log error #4: Clock skew 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. "
+    },
+    "censorship-6": {
+	"id": "#censura-6",
+	"control": "censura-6",
+	"title": "Eu não consigo me conectar ao Navegador Tor, minha rede está censurada?",
+	"description": "<p class=\"mb-3\">Você deve estar em uma internet censurada, e por isso você deve tentar usar pontes. Algumas pontes já são feitas para o Navegador Tor, e você pode usar estas pontes selecionando \"configurar\" (e seguir os passos) na janela de inicialização do Tor que aparece quando você abre o Navegador Tor pela primeira vez. Se você precisar de outras pontes, você pode consegui-las em nosso <mark><a href=\"https://bridges.torproject.org/\">website de Pontes</a></mark>. Para mais informações sobre pontes, veja o <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">manual do Navegador Tor</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ro.json b/ro.json
new file mode 100644
index 000000000..559d4978f
--- /dev/null
+++ b/ro.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Cum descarc Tor dacă torproject.org e blocat?",
+	"description": "<p class=\"mb-3\">Dacă nu poți descărca Tor din <mark><a href=\"https://www.torproject.org\">website</a></mark>, poți obține o o copie a Tor prin intermediul GetTor. GetTor e un serviciu care răspunde automat la mesaje cu legături către ultima versiune de Tor Browser stocata într-o varietate de locuri mai puțin probabil de a fi cenzurate, cum ar fi Dropbox, Google Drive sau Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Am dificultăți în conectarea la Tor și nu înțeleg ce e greșit.",
+	"description": "<p class=\"mb-3\">Dacă aveți probleme de conectare, selectați opțiunea \"copiază log-ul Tor în clipboard\". Apoi lipiți log-ul astfel copiat într-un fișier text sau alt document. Ar trebui să vedeți unul dintre aceste mesaje de eroare comune (căutați astfel de linii în log-ul Tor):</p><h5>Eroare comună #1: Eroare de conectare la proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxx
 xx  (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Dacă vedeți astfel de linii in log-ul Tor, înseamnă că nu vă puteți conecta la un proxy SOCKS. Dacă un proxy SOCKS este necesar pentru rețeaua pe care o folosiți, atunci asigurați-vă că ați introdus setările de proxy corecte. Dacă un proxy SOCKS nu e necesar sau nu sunteți sigur, încercați să vă conectați la rețeaua Tor fără un proxy SOCKS.<p><h5>Eroare comună #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></p
 re></p><p class=\"mb-3\">Dacă vedeți astfel de linii in log-ul Tor înseamnă ca nu s-a reuțit conectarea la primul nod din circuitul Tor. Aceasta ar putea însemna că vă aflați într-o rețea cenzurată. Încercați conectarea prin punți, care ar trebui să rezolve problema.</p><h5>Eroare comună #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Dac
 ă vedeți astfel de linii in log-ul Tor înseamnă că nu s-a realizat o conexiune completă TLS cu serverele de directoare. Folosirea punților va rezolva probabil acest lucru. </p><h5>Eroare comună #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Dacă vedeți astfel de linii in log-ul Tor înseamnă că ceasul sistemului Dvs. e incorect. Asigurați-vă că ceasul sistemului este corect, inclusiv fusul orar, apoi reporn
 iți Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ru.json b/ru.json
new file mode 100644
index 000000000..f937981d6
--- /dev/null
+++ b/ru.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Наш сайт заблокирован цензурой. Смогут ли пользователи получить доступ к сайту через Tor Browser?",
+	"description": "<p class=\"mb-3\">Tor Browser безусловно может помочь людям получить доступ к вашему веб-сайту в местах, где он заблокирован. Большую часть времени простая загрузка <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> и использование его для перехода на заблокированный сайт позволит получить доступ к нему. В местах, где существует усиленная цензура, у нас есть ряд доступных инструментов обхода цензуры, включая <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. За дополнительной информацией, пожалуйста, обратитесь к разделу <mark><a hre
 f=\"https://tb-manual.torproject.org/en-US/circumvention.html\">о цензуре</a></mark> в <mark><a href=\"https://tb-manual.torproject.org/en-US/\">руководстве пользователя Tor Browser</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "Мой любимый сайт блокирует доступ через Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Как загрузить Tor, если torproject.org заблокирован?",
+	"description": "<p class=\"mb-3\">Если Вы не можете скачать Tor через наш <mark><a href=\"https://www.torproject.org\">сайт</a></mark>, вы можете получить копию Tor через GetTor. GetTor - это услуга, которая автоматически отвечает на сообщения ссылками на последнюю версию Tor Browser, размещенные в различных местах, которые менее вероятно подвергаются цензуре, такие как Dropbox, Google Диск и Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "Я не могу подключиться к Tor Browser, моя сеть цензурируется?",
+	"description": "<p class=\"mb-3\">Возможно, вы находитесь в подвергаемой цензуре сети, поэтому вам следует попробовать использовать мосты. Некоторые мосты встроены в Tor Browser, и вы можете использовать эти мосты, выбрав «Настроить» (далее следуя подсказкам) в окне запуска Tor, который всплывает при первом открытии Tor Browser. Если вам нужны другие мосты, вы можете получить их на нашем <mark><a href=\"https://bridges.torproject.org/\">веб-сайте, посвященном мостам</a></mark>. Для получения более подробной информации о мостах, см. <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">руководство Tor Browser</a></mark>.
 </p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "Я не могу подключиться к Tor Browser, моя сеть цензурируется?",
+	"description": "<p class=\"mb-3\">Возможно, вы находитесь в подвергаемой цензуре сети, поэтому вам следует попробовать использовать мосты. Некоторые мосты встроены в Tor Browser, и вы можете использовать эти мосты, выбрав «Настроить» (далее следуя подсказкам) в окне запуска Tor, который всплывает при первом открытии Tor Browser. Если вам нужны другие мосты, вы можете получить их на нашем <mark><a href=\"https://bridges.torproject.org/\">веб-сайте, посвященном мостам</a></mark>. Для получения более подробной информации о мостах, см. <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">руководство Tor Browser</a></mark>.
 </p>"
+    }
+
+
+}
diff --git a/ru at petr1708.json b/ru at petr1708.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ru at petr1708.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/scn.json b/scn.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/scn.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sco.json b/sco.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sco.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/si_LK.json b/si_LK.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/si_LK.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sk.json b/sk.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sk.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sk_SK.json b/sk_SK.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sk_SK.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sl.json b/sl.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sl.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sl_SI.json b/sl_SI.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sl_SI.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sn.json b/sn.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sn.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/so.json b/so.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/so.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/son.json b/son.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/son.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sq.json b/sq.json
new file mode 100644
index 000000000..b4e0cb967
--- /dev/null
+++ b/sq.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Siti ynë është i bllokuar nga një censurë. Mundet Tor të ndihmoje përdoruesit të aksesojn sitin tonë?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sr.json b/sr.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sr.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sr at latin.json b/sr at latin.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sr at latin.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/st.json b/st.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/st.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/su.json b/su.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/su.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/support-censorship.json b/support-censorship.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/support-censorship.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sv.json b/sv.json
new file mode 100644
index 000000000..f7115ef62
--- /dev/null
+++ b/sv.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Vår webbplats är blockerad av en censor. Kan Tor Browser hjälpa användare att komma åt vår webbplats?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "Min favoritwebbplats blockerar åtkomst över Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "Hur laddar jag ner Tor om torproject.org är blockerad?",
+	"description": "Om du inte kan ladda ner Tor på vår <mark><a href=\"https://www.torproject.org\">webbsajt</a></mark>, så kan du få Tor levererat till dig via GetTor. GetTor är en tjänst som automatiskt svarar på meddelanden med länkar till den senaste versionen av Tor Browser, som finns på flera olika platser som sannolikt inte är censurerade, till exempel Dropbox, Google Drive och Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "Jag kan inte ansluta till Tor Browser, är mitt nätverk censurerat?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Jag har problem med att ansluta till Tor, och jag kan inte ta reda på vad som är fel.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "Jag kan inte ansluta till Tor Browser, är mitt nätverk censurerat?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/sw.json b/sw.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sw.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/szl.json b/szl.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/szl.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ta.json b/ta.json
new file mode 100644
index 000000000..2b46484de
--- /dev/null
+++ b/ta.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#தணிக்கை-1",
+	"control": "தணிக்கை-1",
+	"title": "எங்கள் வலைத்தளம் தணிக்கையால் தடுக்கப்பட்டுள்ளது. டார் உலாவி எங்கள் வலைத்தளத்தை அணுக பயனர்களுக்கு உதவ முடியுமா?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/te.json b/te.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/te.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/te_IN.json b/te_IN.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/te_IN.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/tg.json b/tg.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/tg.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/th.json b/th.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/th.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ti.json b/ti.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ti.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/tk.json b/tk.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/tk.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/tr.json b/tr.json
new file mode 100644
index 000000000..a546fcdf0
--- /dev/null
+++ b/tr.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Sitemiz bir denetçi tarafından engellenmiştir. Tor Browser sitemize erişebilmeleri için kullanıcılara yardım etsin mi?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "En sevdiğim website'm Tor'a erişimimi engelliyor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "torproject.org' a erişilemiyorsa Tor 'u nasıl indirebilirim?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "Tor taryıcısına bağlanamıyorum. Bağlantım sıkıntılı mı?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "Tor 'a bağlanmakta sıkıntı çekiyorum ve ne de problem olduğunu bulamıyorum.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "Tor Browser' a bağlanamıyorum. Bağlantım sıkıntılı mı?\n",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/tzm.json b/tzm.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/tzm.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ug at Arab.json b/ug at Arab.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ug at Arab.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/uk.json b/uk.json
new file mode 100644
index 000000000..07e25c48c
--- /dev/null
+++ b/uk.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#цензура-1",
+	"control": "цензура-1",
+	"title": "Наш веб-сайт заблокований цензором. Чи може браузер Tor допомогти користувачам отримати доступ до нашого веб-сайту?",
+	"description": "1"
+    },
+    "censorship-2": {
+	"id": "#цензура-2",
+	"control": "цензура-2",
+	"title": "Мій улюблений веб-сайт блокує доступ через Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#цензура-3",
+	"control": "цензура-3",
+	"title": "Як завантажити Tor, якщо torproject.org заблокований?",
+	"description": "Якщо ви не можете завантажити Tor через наший веб-сайт, ви можете отримати копію Tor, доставлену вам через GetTor. GetTor — це служба, яка автоматично відповідає на повідомлення з посиланнями на останню версію браузера Tor, що розміщується в різних місцях, які, як правило, не підлягають цензурі, таких як Dropbox, Google Диск і Github."
+    },
+    "censorship-4": {
+	"id": "#цензура-4",
+	"control": "цензура-4",
+	"title": "Я не можу підключитися до браузера Tor, чи моя мережа піддається цензурі?",
+	"description": "<p class=\"mb-3\">Ви можете бути у мережі, що цензується, і тому ви повинні спробувати використовувати мости. Деякі мости вбудовані у браузер Tor, і ви можете використовувати ці мости, вибравши \"налаштувати\" (а потім слідувати підказкам) у вікні запуску Tor, що з'явиться під час відкриття браузера Tor вперше. Якщо вам потрібні інші мости, ви можете отримати їх на нашому <mark><a href=\"https://bridges.torproject.org/\">Сайті мостів</a></mark>. Щоб отримати додаткові відомості про мости, перегляньте <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">посібник користувача браузера Tor</a></m
 ark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#цензура-5",
+	"control": "цензура-5",
+	"title": "У мене виникла проблема з під'єднанням до Tor, і я не можу зрозуміти, що не так.",
+	"description": "<p class=\"mb-3\">Якщо у вас виникли проблеми з під'єднанням, виберіть опцію «копіювати журнал Tor у буфер обміну». Потім вставте журнал Tor у текстовий файл або інший документ. Ви маєте побачити одну з цих помилок загального журналу (шукайте наступні рядки в журналі Tor):</p><h5>Помилка загального журналу №1: Помилка з'єднання з проксі-сервером</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"g
 eneral SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p> <p class=\"mb-3\">Ð¯ÐºÑ‰Ð¾ Ð²Ð¸ Ð±Ð°Ñ‡Ð¸Ñ‚Ðµ Ñ‚Ð°ÐºÑ– Ñ€ÑÐ´ÐºÐ¸ Ð² Ð¶ÑƒÑ€Ð½Ð°Ð»Ñ– Tor, Ñ†Ðµ Ð¾Ð·Ð½Ð°Ñ‡Ð°Ñ”, Ñ‰Ð¾ Ð²Ð¸ Ð½Ðµ Ð¼Ð¾Ð¶ÐµÑ‚Ðµ Ð¿Ñ–Ð´'Ñ”Ð´Ð½Ð°Ñ‚Ð¸ÑÑ Ð´Ð¾ Ð¿Ñ€Ð¾ÐºÑÑ– SOCKS. Ð¯ÐºÑ‰Ð¾ Ð´Ð»Ñ Ð½Ð°Ð»Ð°ÑˆÑ‚ÑƒÐ²Ð°Ð½Ð½Ñ Ð¼ÐµÑ€ÐµÐ¶Ñ– Ð¿Ð¾Ñ‚Ñ€Ñ–Ð±ÐµÐ½ Ð¿Ñ€Ð¾ÐºÑÑ–-ÑÐµÑ€Ð²ÐµÑ€ SOCKS, Ð±ÑƒÐ´ÑŒ Ð»Ð°ÑÐºÐ°, Ð¿ÐµÑ€ÐµÐºÐ¾Ð½Ð°Ð¹Ñ‚ÐµÑÑ, Ñ‰Ð¾ Ð²Ð¸ Ð¿Ñ€Ð°Ð²Ð¸Ð»ÑŒÐ½Ð¾ Ð²Ð²ÐµÐ»Ð¸ Ñ–Ð½Ñ„Ð¾Ñ€Ð¼Ð°Ñ†Ñ–ÑŽ Ð¿Ñ€Ð¾ Ð¿Ñ€Ð¾ÐºÑÑ–. Ð¯ÐºÑ‰Ð¾ Ð¿Ñ€Ð¾ÐºÑÑ– SOCKS Ð½Ðµ Ð¿Ð¾Ñ‚Ñ€Ñ–Ð±Ð½Ð¸Ð¹, Ð°Ð±Ð¾ Ð²Ð¸ Ð½Ðµ Ð²Ð¿ÐµÐ²Ð½ÐµÐ½Ñ–, ÑÐ¿Ñ€Ð¾Ð±ÑƒÐ¹Ñ‚Ðµ Ð¿Ñ–Ð´'Ñ”Ð´Ð½Ð°Ñ‚Ð¸ÑÑ Ð´Ð¾ Ð¼ÐµÑ€ÐµÐ¶Ñ– Tor Ð±ÐµÐ· Ð¿Ñ€Ð¾ÐºÑÑ–-ÑÐµÑ€Ð²ÐµÑ€Ð° SOCKS.<p><h5>ÐŸÐ¾Ð¼Ð¸Ð»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑŒÐ½Ð¾Ð³Ð¾ Ð¶ÑƒÑ€Ð½Ð°Ð»Ñƒ â„–2: ÐÐµ Ð²Ð´Ð°Ñ”Ñ‚ÑŒÑÑ Ð
 ´Ñ–ÑÑ‚Ð°Ñ‚Ð¸ÑÑŒ Ð±ÐµÐ·Ð¿ÐµÑ‡Ð½Ð¸Ñ… Ð¿ÐµÑ€ÐµÐ´Ð°Ð²Ð°Ñ‡Ñ–Ð²</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑ‰Ð¾ Ñƒ Ð¶ÑƒÑ€Ð½Ð°Ð»Ñ– Tor Ð²Ð¸ Ð±Ð°Ñ‡Ð¸Ñ‚Ðµ Ñ‚Ð°ÐºÑ– Ñ€ÑÐ´ÐºÐ¸, Ñ‚Ð¾ Ñ†Ðµ Ð¾Ð·Ð½Ð°Ñ‡Ð°Ñ”, Ñ‰Ð¾ Ð²Ð°ÑˆÐ¾Ð¼Ñƒ Tor Ð½Ðµ Ð²Ð´Ð°Ð»Ð¾ÑÑ Ð¿Ñ–Ð´'Ñ”Ð´Ð½Ð°Ñ‚Ð¸ÑÑ Ð´Ð¾ Ð¿ÐµÑ€ÑˆÐ¾Ð³Ð¾ Ð²ÑƒÐ·Ð»Ð° Ð² Ð»Ð°Ð½Ñ†ÑŽÐ·Ñ– Tor. Ð¦Ðµ Ð¼Ð¾Ð¶Ðµ Ð¾Ð·Ð½Ð°Ñ‡Ð°Ñ‚Ð¸, Ñ‰Ð¾ Ð²Ð¸ Ð¿ÐµÑ€ÐµÐ±ÑƒÐ²Ð°Ñ”Ñ‚Ðµ Ñƒ Ð¼ÐµÑ€ÐµÐ¶Ñ–, ÑÐºÐ° Ð¿Ñ–Ð´Ð´Ð°Ñ”Ñ‚ÑŒÑÑ Ñ†ÐµÐ½Ð·ÑƒÑ€Ñ–. Ð‘ÑƒÐ´ÑŒ Ð»Ð°ÑÐºÐ°, ÑÐ¿Ñ€Ð¾Ð±ÑƒÐ¹Ñ‚Ðµ Ð¿Ñ–Ð´ÐºÐ»ÑŽÑ‡Ð¸Ñ‚Ð¸ÑÑ Ð´Ð¾ Ð¼Ð¾Ñ
 Ñ‚Ñ–Ð², Ñ– Ñ†Ðµ Ð¼Ð°Ñ” Ð²Ð¸Ñ€Ñ–ÑˆÐ¸Ñ‚Ð¸ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñƒ.</p><h5>ÐŸÐ¾Ð¼Ð¸Ð»ÐºÐ° Ð·Ð°Ð³Ð°Ð»ÑŒÐ½Ð¾Ð³Ð¾ Ð¶ÑƒÑ€Ð½Ð°Ð»Ñƒ â„–3: Ð½Ðµ Ð²Ð´Ð°Ð»Ð¾ÑÑ Ð·Ð°Ð²ÐµÑ€ÑˆÐ¸Ñ‚Ð¸ Ñ€ÑƒÐºÐ¾ÑÑ‚Ð¸ÑÐºÐ°Ð½Ð½Ñ TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑ‰Ð¾ Ð²Ð¸ Ð±Ð°Ñ‡Ð¸Ñ‚Ðµ Ñ‚Ð°ÐºÑ– Ñ€ÑÐ´ÐºÐ¸ Ð² Ð¶ÑƒÑ€Ð½Ð°Ð»Ñ– Tor, Ñ†Ðµ Ð¾Ð·Ð½Ð°Ñ‡Ð°Ñ”, Ñ‰Ð¾ Tor Ð½Ðµ Ð²Ð´Ð°Ð»Ð¾ÑÑ Ð²Ð¸ÐºÐ¾Ð½Ð°Ñ‚Ð¸ Ñ€ÑƒÐºÐ¾ÑÑ‚Ð¸ÑÐºÐ°Ð½Ð½Ñ
  TLS за допомогою служб каталогу. Використання мостів, швидше за все, буде виправляти це.</p><h5> Помилка загального журналу №4: збитий годинник</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Якщо ви бачите такі рядки в журналі Tor, це означає, що ваш системний годинник непр
 авильний. Будь-ласка, переконайтеся, що ваший годинник встановлений точно, включно з правильним часовим поясом. Потім перезапустіть Tor.</p>"
+    },
+    "censorship-6": {
+	"id": "#цензура-6",
+	"control": "цензура-6",
+	"title": "Я не можу підключитися до браузера Tor, чи моя мережа піддається цензурі?",
+	"description": "<p class=\"mb-3\">Ви можете бути у мережі, що цензується, і тому ви повинні спробувати використовувати мости. Деякі мости вбудовані у браузер Tor, і ви можете використовувати ці мости, вибравши \"налаштувати\" (а потім слідувати підказкам) у вікні запуску Tor, що з'явиться під час відкриття браузера Tor вперше. Якщо вам потрібні інші мости, ви можете отримати їх на нашому <mark><a href=\"https://bridges.torproject.org/\">Сайті мостів</a></mark>. Щоб отримати додаткові відомості про мости, перегляньте <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">посібник користувача браузера Tor</a></m
 ark>.</p>"
+    }
+
+
+}
diff --git a/ur.json b/ur.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ur.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ur_PK.json b/ur_PK.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ur_PK.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/uz.json b/uz.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/uz.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/ve.json b/ve.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ve.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/vi.json b/vi.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/vi.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/wa.json b/wa.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/wa.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/wo.json b/wo.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/wo.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/zh_CN.json b/zh_CN.json
new file mode 100644
index 000000000..69f34533c
--- /dev/null
+++ b/zh_CN.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#审查-1",
+	"control": "审查-1",
+	"title": "我的网站被审查机构屏蔽了，Tor Browser 能帮助用户访问我的网站吗？",
+	"description": "<p class=\"mb-3\">Tor Browser 当然可以帮助人们在网络受审查的地区访问被屏蔽的网站。大多数时候只需要下载<mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser </a></mark>并使用它进行浏览即可。在网络审查十分严格的地区，我们还提供了许多规避措施，例如<mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>。请参阅<mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser 用户手册</a></mark>的<mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">审查</a></mark>章节以获得更多信息。</p>"
+    },
+    "censorship-2": {
+	"id": "#审查-2",
+	"control": "审查-2",
+	"title": "我最爱的网站屏蔽来自 Tor 的访问。",
+	"description": "<p class=\"mb-3\">不能访问你想要的网站真是遗憾呢！有些网站屏蔽了 Tor 因为他们无法分辨出普通 Tor 用户和机器人的区别。根据过去的经验，想要让网站解封来自 Tor 的访问最有效的方法是由用户直接联系网站管理员。也许这样的消息就可以成功：<br />“嗨，在用 Tor Browser 的时候发现你的网站 xyz.com 不允许来自 Tor 的访问，希望你可以重新考虑这个决定。全球各地很多人都在使用 Tor 来保护隐私和对抗审查，屏蔽 Tor 的同时你也屏蔽了强权国家中想自由访问互联网的用户、需要隐藏自己的记者和检举者、想躲避网络跟踪的研究者和普通用户。请站在支持在线隐私和网络自由的立场上，允许 Tor 用户访问 xyz.com，谢谢！”<br />另外，银行这类比较敏感的网站经常进行地区范围的屏蔽。如果你平时只在某个特定的国家使用他们的服务，从位于
 其他国家的出口节点进行访问时你的账号可能就会被冻结。如无法连接 onion 服务，请参阅 <a href=\"http://127.0.0.1:5000/#onionservices-3\">无法连接 x.onion！</a></p>"
+    },
+    "censorship-3": {
+	"id": "#审查-3",
+	"control": "审查-3",
+	"title": "torproject.org 被屏蔽了，怎么下载 Tor？",
+	"description": "<p class=\"mb-3\">如果无法通过我们的<mark><a href=\"https://www.torproject.org\">网站</a></mark>下载 Tor，你可以通过 GetTor 获取 Tor。GetTor 会自动发送下载 Tor Browser 最新版本的链接，由 Dropbox、Google Drive、GitHub 等更难受到审查的网站进行分发。</p>"
+    },
+    "censorship-4": {
+	"id": "#审查-4",
+	"control": "审查-4",
+	"title": "无法连接 Tor，我的网络被审查了吗？",
+	"description": "<p class=\"mb-3\">你可能在使用受审查的网络，请尝试网桥来进行应对。Tor Browser 中内置了一些网桥，你可以在 Tor Browser 首次启动时弹出的 Tor Launcher 窗口中选择“设置”（然后跟随提示）来启用。如果需要其他网桥，我们的<mark><a href=\"https://bridges.torproject.org/\">网桥站点</a></mark>可以提供它们。关于网桥的更多信息请参阅<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser 用户手册</a></mark>。</p>"
+    },
+    "censorship-5": {
+	"id": "#审查-5",
+	"control": "审查-5",
+	"title": "无法连接到 Tor，但我不知道发生了什么什么错误。",
+	"description": "<p class=\"mb-3\">如果您的连接出现问题，请选择“复制Tor日志到剪贴板”选项。然后粘贴Tor日志到文本文件或者其他文档格式。您应该能够在粘贴的Tor日志中发现这些常见问题（请在Tor日志里寻找如下所示的错误）:</p><h5> 常见错误#1: 代理连接失败</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\"> å¦‚æžœæ‚¨çœ‹è§è¿™äº›æç¤ºå‡ºçŽ°åœ¨æ‚¨çš„æ—¥å¿—é‡Œé¢ï¼Œè¿™æ„å‘³ç€æ‚¨è¿žæŽ¥SOCKSä»£ç†å¤±è´¥äº†ã€‚å¦‚æžœæ‚¨çš„ç³»ç»Ÿè®¾ç½®éœ€è¦ä¸€ä¸ªSOCKSä»£ç†, è¯·ä¿è¯æ‚¨æ£ç¡®çš„è¾“å…¥äº†å…³äºŽè¿™ä¸ªä»£ç†çš„é…ç½®ã€‚  å¦‚æžœæ‚¨çš„ç³»ç»Ÿä¸éœ€è¦ä»£ç†ï¼Œæˆ–è€…æ‚¨ä¸æ•¢è‚¯å®šï¼Œè¯·å°è¯•ç›´æŽ¥è¿žæŽ¥Torç½‘ç»œã€‚<p><h5>å¸¸è§é”™è¯¯ #2: æ— æ³•è¿žæŽ¥åˆ°ä¸ç»§</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">å¦‚æžœæ‚¨çœ‹è§è¿™äº›æç¤ºå‡ºçŽ°åœ¨æ‚¨çš„æ—¥å¿—é‡Œé¢ï¼Œè¿™æ„å‘³ç€æ‚
 ¨çš„Torè¿žæŽ¥ Torç½‘ç»œä¸çš„ç¬¬ä¸€ä¸ªèŠ‚ç‚¹å¤±è´¥äº†ã€‚è¿™å¯èƒ½æ„å‘³ç€æ‚¨å¤„äºŽè¢«ç›‘ç®¡çš„ç½‘ç»œä¹‹ä¸ã€‚è¯·å°è¯•é€šè¿‡ç½‘æ¡¥è¿žæŽ¥ï¼Œè¿™åº”è¯¥èƒ½è§£å†³æ‚¨çš„é—®é¢˜ã€‚</p><h5>å¸¸è§æ—¥å¿—é”™è¯¯#3: TLSæ¡æ‰‹å¤±è´¥</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">å¦‚æžœæ‚¨çœ‹è§è¿™äº›æç¤ºå‡ºçŽ°åœ¨æ‚¨çš„æ—¥å¿—é‡Œé¢ï¼Œè¿™æ„å‘³ç€Tor ä¸Žä¸ç»§ç›®å½•æä¾›æœåŠ¡å™¨çš„TLSæ¡æ‰‹å¤±è´¥äº†ã€‚
  使用网桥应该能解决这个问题</p><h5> 常见错误#4: 时间设置错误</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \nTor需要一个准确的时间来维持它的运作。请检查您的时间，时区以及日期设置。</code></pre></p><p class=\"mb-3\">如果您看见这些提示出现在您的日志里面，这意味着您的系统时间设置错误。请确认您的时间设置是正确的，包括正确的时区。然后重新启动Tor。 </p>"
+    },
+    "censorship-6": {
+	"id": "#审查-6",
+	"control": "审查-6",
+	"title": "无法连接 Tor，我的网络被审查了吗？",
+	"description": "<p class=\"mb-3\">你可能在使用受审查的网络，请尝试网桥来进行应对。Tor Browser 中内置了一些网桥，你可以在 Tor Browser 首次启动时弹出的 Tor Launcher 窗口中选择“设置”（然后跟随提示）来启用。如果需要其他网桥，我们的<mark><a href=\"https://bridges.torproject.org/\">网桥站点</a></mark>可以提供它们。关于网桥的更多信息请参阅<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser 用户手册</a></mark>。</p>"
+    }
+
+
+}
diff --git a/zh_HK.json b/zh_HK.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/zh_HK.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/zh_TW.json b/zh_TW.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/zh_TW.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}
diff --git a/zu.json b/zu.json
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/zu.json
@@ -0,0 +1,40 @@
+{
+    "censorship-1": {
+	"id": "#censorship-1",
+	"control": "censorship-1",
+	"title": "Our website is blocked by a censor. Can Tor Browser help users access our website?",
+	"description": "<p class=\"mb-3\">Tor Browser can certainly help people access your website in places where it is blocked. Most of the time, simply downloading the <mark><a href=\"https://www.torproject.org/download/download-easy.html.en\">Tor Browser</a></mark> and then using it to navigate to the blocked site will allow access. In places where there is heavy censorship we have a number of censorship circumvention options available, including <mark><a href=\"https://www.torproject.org/docs/pluggable-transports.html.en\">pluggable transports</a></mark>. For more information, please see the <mark><a href=\"https://tb-manual.torproject.org/en-US/\">Tor Browser User Manual</a></mark> section on <mark><a href=\"https://tb-manual.torproject.org/en-US/circumvention.html\">censorship</a></mark>.</p>"
+    },
+    "censorship-2": {
+	"id": "#censorship-2",
+	"control": "censorship-2",
+	"title": "My favorite website is blocking access over Tor.",
+	"description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
 acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"http://127.0.0.1:5000/#onionservices-3\">I cannot reach X.onion!</a></p>"
+    },
+    "censorship-3": {
+	"id": "#censorship-3",
+	"control": "censorship-3",
+	"title": "How do I download Tor if the torproject.org is blocked?",
+	"description": "<p class=\"mb-3\">If you can't download Tor through our <mark><a href=\"https://www.torproject.org\">website</a></mark>, you can get a copy of Tor delivered to you via GetTor. GetTor is a service that automatically responds to messages with links to the latest version of Tor Browser, hosted at a variety of locations that are less likely to be censored, such as Dropbox, Google Drive, and Github.</p>"
+    },
+    "censorship-4": {
+	"id": "#censorship-4",
+	"control": "censorship-4",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    },
+    "censorship-5": {
+	"id": "#censorship-5",
+	"control": "censorship-5",
+	"title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.",
+	"description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to “copy Tor log to clipboard.” Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly.  If a SOCKS proxy is not required, or you’re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "censorship-6": {
+	"id": "#censorship-6",
+	"control": "censorship-6",
+	"title": "I can’t connect to Tor Browser, is my network censored?",
+	"description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>"
+    }
+
+
+}

