[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

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

To: tor-commits@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-commits] [translation/support-censorship] pulling translations from transifex
From: translation@xxxxxxxxxxxxxx
Date: Fri, 6 Apr 2018 23:28:06 +0000 (UTC)
Delivered-to: archiver@xxxxxxxx
Delivery-date: Fri, 06 Apr 2018 19:29:26 -0400
List-archive: <http://lists.torproject.org/pipermail/tor-commits/>
List-help: <mailto:tor-commits-request@lists.torproject.org?subject=help>
List-id: "auto: code repository commits" <tor-commits.lists.torproject.org>
List-post: <mailto:tor-commits@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits>, <mailto:tor-commits-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-commits>, <mailto:tor-commits-request@lists.torproject.org?subject=unsubscribe>
Patch-author: Translation commit bot <translation@xxxxxxxxxxxxxx>
Sender: "tor-commits" <tor-commits-bounces@xxxxxxxxxxxxxxxxxxxx>

commit f0b627c73ebe13e1d5b9ce9f0e0d3af38bc505c8
Author: Translation commit bot <translation@xxxxxxxxxxxxxx>
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@xxxxxxxxxxxxx        | 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@xxxxxxxxxx           | 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@xxxxxxxxx            | 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@xxxxxxxxxxxxx b/ru@xxxxxxxxxxxxx
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ru@xxxxxxxxxxxxx
@@ -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@xxxxxxxxxx b/sr@xxxxxxxxxx
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/sr@xxxxxxxxxx
@@ -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@xxxxxxxxx b/ug@xxxxxxxxx
new file mode 100644
index 000000000..33c6fc15d
--- /dev/null
+++ b/ug@xxxxxxxxx
@@ -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>"
+    }
+
+
+}

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

Prev by Author: [tor-commits] [translation/support-tbb] Update translations for support-tbb
Next by Author: [tor-commits] [translation/support-connecting] pulling translations from transifex
Previous by thread: [tor-commits] [tor/release-0.3.3] Ship all files needed to build Tor with rust
Next by thread: [tor-commits] [translation/support-censorship_completed] pulling translations from transifex
Index(es):
- Author
- Thread