replaced all github flavored code blocks with fenced kramdown code blocks

developers/debugging/AutomatedTests.md

@@ -115,7 +115,7 @@ compiled version to the right directory in the RPM file. I.e. adding `example.py
 ### Editing \_\_init\_\_.py
 Add at the bottom of the file in the method `def load_tests` to the variable
 `modname` your test. I.e adding `example.py`.
-```python
+~~~python
     for modname in (
             'qubes.tests.basic',
             'qubes.tests.dom0_update',
@@ -126,4 +126,4 @@ Add at the bottom of the file in the method `def load_tests` to the variable
             'qubes.tests.regressions',
             'qubes.tests.example', # This is our newly added test
             ):
-```
+~~~

developers/debugging/Profiling.md

@@ -15,17 +15,17 @@ For the purpose of this document, `qubes-dev` is name of the domain used for pos
 Requirements
 ------------
 
-```
+~~~
 yum install gprof2dot graphviz
 git clone http://git.woju.eu/qubes/profiling.git
-```
+~~~
 
 If you profile something on dom0, move `Upload.sh` from repository to dom0:
 
-```
+~~~
 mkdir -p ~/profiling
 qvm-run -p qubes-dev 'cat ~/profiling/Upload.sh' > ~/profiling/Upload.sh
-```
+~~~
 
 -   WARNING: this will obviously be running third party code which is not signed by ITL nor Fedora. You have been warned.
 
@@ -62,28 +62,28 @@ Remember to revert your changes to application afterwards.
 
 If you are in dom0:
 
-```
+~~~
 cd ~/profiling
 ./Upload.sh
-```
+~~~
 
 ### Analyse
 
-```
+~~~
 make
-```
+~~~
 
 For every `${basename}.pstats` this will produce `${basename}.txt` and `${basename}.svg`. SVG contains call graph. Text file contains list of all functions sorted by cumulative execution time. You may also try `make all-png`.
 
-```
+~~~
 make index.html
-```
+~~~
 
 This creates `index.html` with all SVG graphics linked to TXT files. Ready for upload.
 
-```
+~~~
 make REMOTE=example.com:public_html/qubes/profiling/ upload
-```
+~~~
 
 Example
 -------

developers/debugging/TestBench.md

@@ -57,9 +57,9 @@ Now configure your DHCP server so your testbench gets static IP and connect your
 
 Install `openssh-server` on your testbench:
 
-```
+~~~
 yum install openssh-server
-```
+~~~
 
 Ensure that sudo works without password from your user account (it should by default).
 
@@ -70,19 +70,19 @@ Development VM
 
 Arrange firewall so you can reach the testbench from your `qubes-dev` VM. Generate SSH key in `qubes-dev`:
 
-```
+~~~
 ssh-keygen -t ecdsa -b 521
-```
+~~~
 
 Add the following section in `.ssh/config` in `qubes-dev`:
 
-```
+~~~
 Host testbench
     # substitute username in testbench
     User user
     # substitute address of your testbench
     HostName 192.168.123.45
-```
+~~~
 
 Then connect to your testbench and paste newly generated `id_ecdsa.pub` to `.ssh/authorized_keys` on testbench so you can log in without entering password every time.
 

developers/debugging/WindowsDebugging.md

@@ -46,7 +46,7 @@ Things get complicated if you need to perform kernel debugging or troubleshoot p
 -   Run the above shell script in dom0.
 -   If everything is fine you should see the proper kernel debugging output in WinDbg. However, if you see something like that:
 
-    ```
+    ~~~
     Opened \\.\com1
     Waiting to reconnect...
     Connected to Windows 7 7601 x64 target at (Wed Mar 19 20:35:43.262 2014 (UTC + 1:00)), ptr64 TRUE
@@ -66,7 +66,7 @@ Things get complicated if you need to perform kernel debugging or troubleshoot p
     **************************************************************************
     Unable to read debugger data block header
     **************************************************************************
-    ```
+    ~~~
 
     ...then you're most likely a victim of the CRLF issue mentioned above. To get around it I wrote a small utility that basically does what socat would do and additionally corrects those replaced bytes in the stream. It's not pretty but it works:
 
@@ -193,7 +193,7 @@ Things get complicated if you need to perform kernel debugging or troubleshoot p
 
 > With this everything should be good:
 >
-> ```
+> ~~~
 > Opened \\.\com1
 > Waiting to reconnect...
 > Connected to Windows 7 7601 x64 target at (Wed Mar 19 20:56:31.371 2014 (UTC + 1:00)), ptr64 TRUE
@@ -205,6 +205,6 @@ Things get complicated if you need to perform kernel debugging or troubleshoot p
 > Machine Name:
 > Kernel base = 0xfffff800`0261a000 PsLoadedModuleList = 0xfffff800`0285d6d0
 > System Uptime: not available
-> ```
+> ~~~
 
 Happy debugging!