OpenKinect
diff --git a/‎README.md‎
Lines changed: 1 addition & 1 deletion b/‎README.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎rules/90-kinect2.rules‎ ‎platform/linux/udev/90-kinect2.rules‎rules/90-kinect2.rules renamed to platform/linux/udev/90-kinect2.rules b/‎rules/90-kinect2.rules‎ ‎platform/linux/udev/90-kinect2.rules‎rules/90-kinect2.rules renamed to platform/linux/udev/90-kinect2.rules
diff --git a/‎tracing/Readme.tracing.txt‎ ‎…tform/windows/tracing/Readme.tracing.txt‎tracing/Readme.tracing.txt renamed to platform/windows/tracing/Readme.tracing.txt b/‎tracing/Readme.tracing.txt‎ ‎…tform/windows/tracing/Readme.tracing.txt‎tracing/Readme.tracing.txt renamed to platform/windows/tracing/Readme.tracing.txt
diff --git a/‎tracing/starttrace.bat‎ ‎platform/windows/tracing/starttrace.bat‎tracing/starttrace.bat renamed to platform/windows/tracing/starttrace.bat b/‎tracing/starttrace.bat‎ ‎platform/windows/tracing/starttrace.bat‎tracing/starttrace.bat renamed to platform/windows/tracing/starttrace.bat
diff --git a/‎tracing/stoptrace.bat‎ ‎platform/windows/tracing/stoptrace.bat‎tracing/stoptrace.bat renamed to platform/windows/tracing/stoptrace.bat b/‎tracing/stoptrace.bat‎ ‎platform/windows/tracing/stoptrace.bat‎tracing/stoptrace.bat renamed to platform/windows/tracing/stoptrace.bat
diff --git a/‎tracing/timestamp.bat‎ ‎platform/windows/tracing/timestamp.bat‎tracing/timestamp.bat renamed to platform/windows/tracing/timestamp.bat b/‎tracing/timestamp.bat‎ ‎platform/windows/tracing/timestamp.bat‎tracing/timestamp.bat renamed to platform/windows/tracing/timestamp.bat
@@ -49,7 +49,7 @@ No. It's a pure USB3 device due to the high bandwidth requirements.
 
 ### Protonect complains about "no device connected" or "failure opening device".
 
-Either your device is connected to an USB2-only port (see above), or you don't have permissions to access the device. On Linux, try running Protonect as root (e.g. using `sudo`). If that fixes things, place `rules/90-kinect2.rules` into `/etc/udev/rules.d/` and re-plug the device.
+Either your device is connected to an USB2-only port (see above), or you don't have permissions to access the device. On Linux, try running Protonect as root (e.g. using `sudo`). If that fixes things, place `platform/linux/udev/90-kinect2.rules` into `/etc/udev/rules.d/` and re-plug the device.
 
 On Linux, also check `dmesg`. If there are warnings like `usb 4-1.1: Not enough bandwidth for new device state.` it means the hardware does not have the capacity for USB3 even if it claims so, or its capacity is not well supported.