f Fix LSPS0 links

blip-0055.md

@@ -354,20 +354,20 @@ The LSP creates a timestamp of when the notification is
 created, then signs both the timestamp and the above body.
 
 The signature is by the LSP using its node ID for signing
-as described in [<LSPS0 ln_signature>][].
+as described in <[LSPS0.ln_signature][]>.
 
-[<LSPS0 ln_signature>]: ./blip-0050.md#link-lsps0ln_signature
+[LSPS0.ln_signature]: ./blip-0050.md#link-lsps0ln_signature
 
 The message to be signed is the following JSON string template:
 
     "LSPS5: DO NOT SIGN THIS MESSAGE MANUALLY: LSP: At ${timestamp} I notify ${body}"
 
 Where `${timestamp}` is the timestamp, in ISO8601
-date format `YYYY-MM-DDThh:mm:ss.uuuZ` [<LSPS0 datetime>][],
+date format `YYYY-MM-DDThh:mm:ss.uuuZ` <[LSPS0.datetime][]>,
 and `${body}` is the exact and complete JSON serialization of
 the above webhook notification object.
 
-[<LSPS0 datetime>]: ./blip-0050.md#link-lsps0datetime
+[LSPS0.datetime]: ./blip-0050.md#link-lsps0datetime
 
 For example, if the timestamp is `2023-05-04T10:52:58.395Z`
 and the webhook notification object is the exact ASCII sequence
@@ -397,7 +397,7 @@ following hex dump:
 ```
 
 The resulting signature is a zbase32-formatted string.
-See [<LSPS0 ln_signature>][] for more information.
+See <[LSPS0 ln_signature][]> for more information.
 
 The timestamp, signature, and webhook notification object are sent
 to the notification delivery service based on the protocol of the