Fix internal link

Author: rmosolgo

guides/subscriptions/ably_implementation.md

@@ -130,7 +130,7 @@ For better performance reading and writing to Redis, you can pass a `connection_
 
 ### Broadcasts
 
-If you set up {% internal_link "Broadcasts", "/subscriptions/broadcasts" %}, then you can update many clients over a single Ably channel.
+If you set up {% internal_link "Broadcasts", "/subscriptions/broadcast" %}, then you can update many clients over a single Ably channel.
 
 Broadcast channels have stable, predictable IDs. To prevent unauthorized clients from "listening in," use [token authorization](#authorization) for transport. Broadcasts channels use the namespace `gqlbdcst:`, so you can provide capabilities to receive them using `"gqlbdcst:*" => [ ... ]` in your authorization code. (If you're using [encryption](#encryption), the prefix will be `ablyencr-gqlbdcst:` instead.)
 

guides/subscriptions/pusher_implementation.md

@@ -118,7 +118,7 @@ For better performance reading and writing to Redis, you can pass a `connection_
 
 ### Broadcasts
 
-If you set up {% internal_link "Broadcasts", "/subscriptions/broadcasts" %}, then you can update many clients over a single Pusher channel.
+If you set up {% internal_link "Broadcasts", "/subscriptions/broadcast" %}, then you can update many clients over a single Pusher channel.
 
 Broadcast channels have stable, predictable IDs. To prevent unauthorized clients from "listening in," use an [authorized Pusher channel](#authorization) for transport. In your authorization code, you can check for a broadcast using `.broadcast_subscription_id?`: