diff --git a/Custom-FTC-Blocks-(myBlocks).md b/Custom-FTC-Blocks-(myBlocks).md
index 831670e..4cdf243 100644
--- a/Custom-FTC-Blocks-(myBlocks).md
+++ b/Custom-FTC-Blocks-(myBlocks).md
@@ -121,7 +121,7 @@ In the **```key```** socket, type **A greeting for you**.  At the **```text```**
 
 <br>**<i>Congratulations!</i>**  You are now an OnBot Java programmer and myBlocks creator.
 
-> <i>For extra fun: try the **Telemetry.speak** Block, followed by a 1500 millisecond **```.sleep```** Block.  You can learn more about DS spoken telemetry at [this separate tutorial](https://github.com/WestsideRobotics/FTC-DS-Speech/wiki).</i>
+> <i>For extra fun: try the **Telemetry.speak** Block, followed by a 1500 millisecond **```.sleep```** Block.  You can learn more about DS spoken telemetry at [this separate tutorial](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Driver-Station-Speech-Telemetry).</i>
 
 This tutorial has three more sections with myBlocks guidelines, followed by **six examples** for you to re-type in OnBot Java and test in Blocks.  Enjoy!
 
@@ -295,7 +295,7 @@ As programmer, you could modify this example in many ways, such as:
 
 # Timer Example
 
-FTC **timers** offer much more capability than the familiar ```.sleep``` Block.  Java programmers can learn about timers from [this Blocks tutorial](https://github.com/WestsideRobotics/FTC-Timers/wiki); you can easily apply its lessons to Java programs.
+FTC **timers** offer much more capability than the familiar ```.sleep``` Block.  Java programmers can learn about timers from [this Blocks tutorial](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Timers-in-FTC-Blocks); you can easily apply its lessons to Java programs.
 
 When creating myBlocks, be careful when converting or 'packaging' a section of existing Java code into a myBlock method.  As a programmer, you must consider **where** your myBlock might be placed in the OpMode.  For example, if the myBlock is placed inside a **repeat while loop**, the Java method will be called many times -- this may or may not be what you intended.  Use the annotation **comment** to tell the Blocks user how your myBlock should be run, including looping (or not).