lnrpc: fix typo in rpc docs

This commit is contained in:
Keagan McClelland committed 2024-01-11 14:08:31 -08:00
1 parent 2ae6b586e3
commit ec854e4dae
3 files changed
+4 -4

No files matched your search

+1 -1
View File
@@ -329,7 +329,7 @@ service Lightning {
optionally specify the add_index and/or the settle_index. If the add_index optionally specify the add_index and/or the settle_index. If the add_index
is specified, then we'll first start by sending add invoice events for all is specified, then we'll first start by sending add invoice events for all
invoices with an add_index greater than the specified value. If the invoices with an add_index greater than the specified value. If the
settle_index is specified, the next, we'll send out all settle events for settle_index is specified, then next, we'll send out all settle events for
invoices with a settle_index greater than the specified value. One or both invoices with a settle_index greater than the specified value. One or both
of these fields can be set. If no fields are set, then we'll only send out of these fields can be set. If no fields are set, then we'll only send out
the latest add/settle events. the latest add/settle events.
+1 -1
View File
@@ -1831,7 +1831,7 @@
}, },
"/v1/invoices/subscribe": { "/v1/invoices/subscribe": {
"get": { "get": {
"summary": "SubscribeInvoices returns a uni-directional stream (server -\u003e client) for\nnotifying the client of newly added/settled invoices. The caller can\noptionally specify the add_index and/or the settle_index. If the add_index\nis specified, then we'll first start by sending add invoice events for all\ninvoices with an add_index greater than the specified value. If the\nsettle_index is specified, the next, we'll send out all settle events for\ninvoices with a settle_index greater than the specified value. One or both\nof these fields can be set. If no fields are set, then we'll only send out\nthe latest add/settle events.", "summary": "SubscribeInvoices returns a uni-directional stream (server -\u003e client) for\nnotifying the client of newly added/settled invoices. The caller can\noptionally specify the add_index and/or the settle_index. If the add_index\nis specified, then we'll first start by sending add invoice events for all\ninvoices with an add_index greater than the specified value. If the\nsettle_index is specified, then next, we'll send out all settle events for\ninvoices with a settle_index greater than the specified value. One or both\nof these fields can be set. If no fields are set, then we'll only send out\nthe latest add/settle events.",
"operationId": "Lightning_SubscribeInvoices", "operationId": "Lightning_SubscribeInvoices",
"responses": { "responses": {
"200": { "200": {
+2 -2
View File
@@ -233,7 +233,7 @@ type LightningClient interface {
// optionally specify the add_index and/or the settle_index. If the add_index // optionally specify the add_index and/or the settle_index. If the add_index
// is specified, then we'll first start by sending add invoice events for all // is specified, then we'll first start by sending add invoice events for all
// invoices with an add_index greater than the specified value. If the // invoices with an add_index greater than the specified value. If the
// settle_index is specified, the next, we'll send out all settle events for // settle_index is specified, then next, we'll send out all settle events for
// invoices with a settle_index greater than the specified value. One or both // invoices with a settle_index greater than the specified value. One or both
// of these fields can be set. If no fields are set, then we'll only send out // of these fields can be set. If no fields are set, then we'll only send out
// the latest add/settle events. // the latest add/settle events.
@@ -1554,7 +1554,7 @@ type LightningServer interface {
// optionally specify the add_index and/or the settle_index. If the add_index // optionally specify the add_index and/or the settle_index. If the add_index
// is specified, then we'll first start by sending add invoice events for all // is specified, then we'll first start by sending add invoice events for all
// invoices with an add_index greater than the specified value. If the // invoices with an add_index greater than the specified value. If the
// settle_index is specified, the next, we'll send out all settle events for // settle_index is specified, then next, we'll send out all settle events for
// invoices with a settle_index greater than the specified value. One or both // invoices with a settle_index greater than the specified value. One or both
// of these fields can be set. If no fields are set, then we'll only send out // of these fields can be set. If no fields are set, then we'll only send out
// the latest add/settle events. // the latest add/settle events.