Remove en/ from URLs (QubesOS/qubes-issues#1333)

developers/debugging/automated-tests.md

@@ -1,8 +1,10 @@
 ---
 layout: doc
 title: Automated Tests
-permalink: /en/doc/automated-tests/
-redirect_from: /doc/AutomatedTests/
+permalink: /doc/automated-tests/
+redirect_from:
+- /en/doc/automated-tests/
+- /doc/AutomatedTests/
 ---
 
 Automatic tests
@@ -104,7 +106,7 @@ Example test run:
 After you added a new unit test to [core-admin/tests](https://github.com/QubesOS/qubes-core-admin/tree/master/tests) 
 you have to make sure of two things:
 
-1. The test will be added to the RPM file created by [QubesBuilder](/en/doc/qubes-builder/) 
+1. The test will be added to the RPM file created by [QubesBuilder](/doc/qubes-builder/) 
 For this you need to edit [core-admin/tests/Makefile](https://github.com/QubesOS/qubes-core-admin/tree/master/tests/Makefile)
 2. The test will be loaded by [core-admin/tests/\_\_init\_\_.py](https://github.com/QubesOS/qubes-core-admin/tree/master/tests/__init__.py)
 

developers/debugging/profiling.md

@@ -1,8 +1,9 @@
 ---
 layout: doc
 title: Profiling
-permalink: /en/doc/profiling/
+permalink: /doc/profiling/
 redirect_from:
+- /en/doc/profiling/
 - /doc/Profiling/
 - /wiki/Profiling/
 ---

developers/debugging/test-bench.md

@@ -1,8 +1,9 @@
 ---
 layout: doc
 title: Test Bench
-permalink: /en/doc/test-bench/
+permalink: /doc/test-bench/
 redirect_from:
+- /en/doc/test-bench/
 - /doc/TestBench/
 - /wiki/TestBench/
 ---
@@ -12,7 +13,7 @@ Test bench for Dom0
 
 This guide shows how to set up simple test bench that automatically test your code you're about to push. It is written especially for `core3` branch of `core-admin.git` repo, but some ideas are universal.
 
-We will set up a spare machine (bare metal, not a virtual) that will be hosting our experimental Dom0. We will communicate with it via Ethernet and SSH. This tutorial assumes you are familiar with [QubesBuilder](/en/doc/qubes-builder/) and you have it set up and running flawlessly.
+We will set up a spare machine (bare metal, not a virtual) that will be hosting our experimental Dom0. We will communicate with it via Ethernet and SSH. This tutorial assumes you are familiar with [QubesBuilder](/doc/qubes-builder/) and you have it set up and running flawlessly.
 
 Setting up the machine
 ----------------------

developers/debugging/vm-interface.md

@@ -1,11 +1,12 @@
 ---
 layout: doc
 title: VM Configuration Interface
-permalink: /en/doc/vm-interface/
+permalink: /doc/vm-interface/
 redirect_from:
+- /en/doc/vm-interface/
 - /doc/VMInterface/
-- "/doc/SystemDoc/VMInterface/"
-- "/wiki/SystemDoc/VMInterface/"
+- /doc/SystemDoc/VMInterface/
+- /wiki/SystemDoc/VMInterface/
 ---
 
 VM Configuration Interface
@@ -83,16 +84,16 @@ Other Qrexec services installed by default:
 - `qubes.DetachPciDevice` - service called in reaction to `qvm-pci -d` call on
   running VM. The service receives one word - BDF of device to detach. When the
   service call ends, the device will be detached
-- `qubes.Filecopy` - receive some files from other VM. Files sent in [qfile format](/en/doc/qfilecopy/)
+- `qubes.Filecopy` - receive some files from other VM. Files sent in [qfile format](/doc/qfilecopy/)
 - `qubes.OpenInVM` - open a file in called VM. Service receives a single file on stdin (in
-  [qfile format](/en/doc/qfilecopy/). After a file viewer/editor is terminated, if
+  [qfile format](/doc/qfilecopy/). After a file viewer/editor is terminated, if
   the file was modified, can be sent back (just raw content, without any
   headers); otherwise service should just terminate without sending anything.
   This service is used by both `qvm-open-in-vm` and `qvm-open-in-dvm` tools. When
   called in DispVM, service termination will trigger DispVM cleanup.
 - `qubes.Restore` - retrieve Qubes backup. The service receives backup location
   entered by the user (one line, terminated by '\n'), then should output backup
-  archive in [qfile format](/en/doc/qfilecopy/) (core-agent-linux component contains
+  archive in [qfile format](/doc/qfilecopy/) (core-agent-linux component contains
   `tar2qfile` utility to do the conversion
 - `qubes.SelectDirectory`, `qubes.SelectFile` - services which should show
   file/directory selection dialog and return (to stdout) a single line
@@ -118,7 +119,7 @@ abstraction. This will change in the future. Those tools are:
 - `nm-online -x` - called before `qubes.SyncNtpClock` service call by `qvm-sync-clock` tool
 - `resize2fs` - called to resize filesystem on /rw partition by `qvm-grow-private` tool
 - `gpk-update-viewer` - called by Qubes Manager to display available updates in a TemplateVM
-- `systemctl start qubes-update-check.timer` (and similarly stop) - called when enabling/disabling updates checking in given VM (`qubes-update-check` [qvm-service](/en/doc/qubes-service/))
+- `systemctl start qubes-update-check.timer` (and similarly stop) - called when enabling/disabling updates checking in given VM (`qubes-update-check` [qvm-service](/doc/qubes-service/))
 
 Additionally automatic tests extensively calls various commands directly in VMs. We do not plan to change that.
 

developers/debugging/windows-debugging.md

@@ -1,8 +1,9 @@
 ---
 layout: doc
 title: Windows Debugging
-permalink: /en/doc/windows-debugging/
+permalink: /doc/windows-debugging/
 redirect_from:
+- /en/doc/windows-debugging/
 - /doc/WindowsDebugging/
 - /wiki/WindowsDebugging/
 ---