diff --git a/docs/development/device/client-api.mdx b/docs/development/device/client-api.mdx
index 5dc992c0..0f225e57 100644
--- a/docs/development/device/client-api.mdx
+++ b/docs/development/device/client-api.mdx
@@ -31,7 +31,7 @@ The receiver will validate length and if >512 it will assume the packet is corru
 
 This is the main Bluetooth service for the device and provides the API your app should use to get information about the mesh, send packets, or provision the radio.
 
-For a reference implementation of a client that uses this service see [RadioInterfaceService](https://github.com/meshtastic/Meshtastic-Android/blob/master/app/src/main/java/com/geeksville/mesh/service/RadioInterfaceService.kt).
+For a reference implementation of a client that uses this service see [RadioInterfaceService](https://github.com/meshtastic/Meshtastic-Android/blob/master/app/src/main/java/com/geeksville/mesh/repository/radio/RadioInterfaceService.kt).
 
 Typical flow when a phone connects to the device should be the following (if you want to watch this flow from the python app just run `meshtastic --debug --info` - the flow over BLE is identical):
 
@@ -53,7 +53,7 @@ Expected sequence for initial download:
 - Read a endConfig packet that indicates that the entire state you need has been sent
 - Read a series of MeshPackets until it returns empty to get any messages that arrived for this node while the phone was away
 
-For definitions (and documentation) on FromRadio, ToRadio, MyNodeInfo, NodeInfo and User protocol buffers see [mesh.proto](https://github.com/meshtastic/protobufs/blob/master/mesh.proto)
+For definitions (and documentation) on FromRadio, ToRadio, MyNodeInfo, NodeInfo and User protocol buffers see [mesh.proto](https://github.com/meshtastic/protobufs/blob/master/meshtastic/mesh.proto)
 
 UUID for the service: 6ba1b218-15a8-461f-9fa8-5dcae273eafd