From 6e916f2e40bd713c1a22b5b981b392cb357c8f06 Mon Sep 17 00:00:00 2001 From: Gabriel Comte Date: Fri, 17 Jul 2020 16:10:29 +0200 Subject: [PATCH] looprpc/docs: fix typo --- looprpc/client.pb.go | 4 ++-- looprpc/client.proto | 4 ++-- looprpc/client.swagger.json | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/looprpc/client.pb.go b/looprpc/client.pb.go index 8bc9e32..d6bcd14 100644 --- a/looprpc/client.pb.go +++ b/looprpc/client.pb.go @@ -138,7 +138,7 @@ type LoopOutRequest struct { //Maximum amount of the swap fee that may be charged as a prepayment. MaxPrepayAmt int64 `protobuf:"varint,6,opt,name=max_prepay_amt,json=maxPrepayAmt,proto3" json:"max_prepay_amt,omitempty"` //* - //Maximum in on-chain fees that we are willing to spent. If we want to + //Maximum in on-chain fees that we are willing to spend. If we want to //sweep the on-chain htlc and the fee estimate turns out higher than this //value, we cancel the swap. If the fee estimate is lower, we publish the //sweep tx. @@ -294,7 +294,7 @@ type LoopInRequest struct { //response of the GetQuote call. MaxSwapFee int64 `protobuf:"varint,2,opt,name=max_swap_fee,json=maxSwapFee,proto3" json:"max_swap_fee,omitempty"` //* - //Maximum in on-chain fees that we are willing to spent. If we want to + //Maximum in on-chain fees that we are willing to spend. If we want to //publish the on-chain htlc and the fee estimate turns out higher than this //value, we cancel the swap. // diff --git a/looprpc/client.proto b/looprpc/client.proto index cfb7f3a..ba84cda 100644 --- a/looprpc/client.proto +++ b/looprpc/client.proto @@ -145,7 +145,7 @@ message LoopOutRequest { int64 max_prepay_amt = 6; /** - Maximum in on-chain fees that we are willing to spent. If we want to + Maximum in on-chain fees that we are willing to spend. If we want to sweep the on-chain htlc and the fee estimate turns out higher than this value, we cancel the swap. If the fee estimate is lower, we publish the sweep tx. @@ -208,7 +208,7 @@ message LoopInRequest { int64 max_swap_fee = 2; /** - Maximum in on-chain fees that we are willing to spent. If we want to + Maximum in on-chain fees that we are willing to spend. If we want to publish the on-chain htlc and the fee estimate turns out higher than this value, we cancel the swap. diff --git a/looprpc/client.swagger.json b/looprpc/client.swagger.json index c27066b..e6fd84e 100644 --- a/looprpc/client.swagger.json +++ b/looprpc/client.swagger.json @@ -381,7 +381,7 @@ "max_miner_fee": { "type": "string", "format": "int64", - "description": "*\nMaximum in on-chain fees that we are willing to spent. If we want to\npublish the on-chain htlc and the fee estimate turns out higher than this\nvalue, we cancel the swap. \n\nmax_miner_fee is typically taken from the response of the GetQuote call." + "description": "*\nMaximum in on-chain fees that we are willing to spend. If we want to\npublish the on-chain htlc and the fee estimate turns out higher than this\nvalue, we cancel the swap. \n\nmax_miner_fee is typically taken from the response of the GetQuote call." }, "last_hop": { "type": "string", @@ -435,7 +435,7 @@ "max_miner_fee": { "type": "string", "format": "int64", - "description": "*\nMaximum in on-chain fees that we are willing to spent. If we want to\nsweep the on-chain htlc and the fee estimate turns out higher than this\nvalue, we cancel the swap. If the fee estimate is lower, we publish the\nsweep tx.\n\nIf the sweep tx is not confirmed, we are forced to ratchet up fees until it\nis swept. Possibly even exceeding max_miner_fee if we get close to the htlc\ntimeout. Because the initial publication revealed the preimage, we have no\nother choice. The server may already have pulled the off-chain htlc. Only\nwhen the fee becomes higher than the swap amount, we can only wait for fees\nto come down and hope - if we are past the timeout - that the server is not\npublishing the revocation.\n\nmax_miner_fee is typically taken from the response of the GetQuote call." + "description": "*\nMaximum in on-chain fees that we are willing to spend. If we want to\nsweep the on-chain htlc and the fee estimate turns out higher than this\nvalue, we cancel the swap. If the fee estimate is lower, we publish the\nsweep tx.\n\nIf the sweep tx is not confirmed, we are forced to ratchet up fees until it\nis swept. Possibly even exceeding max_miner_fee if we get close to the htlc\ntimeout. Because the initial publication revealed the preimage, we have no\nother choice. The server may already have pulled the off-chain htlc. Only\nwhen the fee becomes higher than the swap amount, we can only wait for fees\nto come down and hope - if we are past the timeout - that the server is not\npublishing the revocation.\n\nmax_miner_fee is typically taken from the response of the GetQuote call." }, "loop_out_channel": { "type": "string",