Add consistency to the event structure in (NWC).
Currently, requests and responses have different keys to identify their method type, which may cause confusion or misunderstandings.
This change aims to standardize the key names across all request and response events, making it easier for developers to understand and implement the protocol
The response section that explained how the multi_pay_invoice method worked had a grammatical error of explaining the differentiation between requests.
changed ".....contains an d tag" to "...contains a d tag"
This adds an optional but recommended lud16 parameter to nostr wallet
connection strings. This enables seamless onboarding of new users,
allowing clients to automatically configure the receive address for
zaps.
