Fix links to old manual URLs.

Core.md

@@ -32,7 +32,7 @@ The **TO DEVICE** section sends Rack signals to a hardware audio device for play
 After a driver is selected, a particular **device** can be chosen for the driver.
 
 The **sample rate** is the number of audio samples per second for the audio device to process.
-Note that this rate is different than Rack's [engine sample rate](https://vcvrack.com/manual/MenuBar#sample-rate), which determines the number of samples per second for Rack modules to process.
+Note that this rate is different than Rack's [engine sample rate](MenuBar#sample-rate), which determines the number of samples per second for Rack modules to process.
 If set to different rates, sample rate conversion will occur, resulting in slightly higher CPU usage, slightly less audio fidelity, and slightly more latency.
 
 The **block size** sets the number of samples to store in the audio buffer before releasing to the audio device.

PluginDevelopmentTutorial.md

@@ -115,7 +115,7 @@ Then add the following code to the `process()` function, which is called every a
 		// Compute the sine output
 		float sine = std::sin(2.f * M_PI * phase);
 		// Audio signals are typically +/-5V
-		// https://vcvrack.com/manual/VoltageStandards.html
+		// https://manual.vcvrack.com/VoltageStandards
 		outputs[SINE_OUTPUT].setVoltage(5.f * sine);
 
 		// Blink light at 1Hz
@@ -128,7 +128,7 @@ Then add the following code to the `process()` function, which is called every a
 Compile your plugin with `make`.
 If the build succeeds, you can generate a distributable plugin package with `make dist`, which places it in `dist/`.
 
-You can automatically install the plugin package to your [Rack user folder](https://vcvrack.com/manual/FAQ#where-is-the-rack-user-folder) with `make install`.
+You can automatically install the plugin package to your [Rack user folder](manual/FAQ#where-is-the-rack-user-folder) with `make install`.
 You should now be able to test your plugin by opening Rack and choosing your module in the Module Browser.
 
 If you don't see your plugin in Rack's Module Browser, check the `log.txt` file in your Rack user folder.