askrene: inform-channel fixes argument order

The documentation and the implementation of inform-channel have
different orders for the arguments minimum_msat and maximum_msat.
We change the order in the documentation to match that of the
implementation: minimum_msat comes before maximum_msat.

Signed-off-by: Lagrang3 <lagrang3@protonmail.com>
This commit is contained in:
Lagrang3 2024-08-12 20:26:55 +01:00 committed by ShahanaFarooqui
parent 3f32f9ea10
commit 4ac85b2cd1
2 changed files with 12 additions and 12 deletions

View File

@ -446,17 +446,17 @@
"The direction to apply this change to."
]
},
"maximum_msat": {
"type": "msat",
"description": [
"The maximum value which this channel could pass. This or *minimum_msat* must be specified, but not both."
]
},
"minimum_msat": {
"type": "msat",
"description": [
"The minumum value which this channel could pass. This or *minimum_msat* must be specified, but not both."
]
},
"maximum_msat": {
"type": "msat",
"description": [
"The maximum value which this channel could pass. This or *minimum_msat* must be specified, but not both."
]
}
}
},

View File

@ -34,17 +34,17 @@
"The direction to apply this change to."
]
},
"maximum_msat": {
"type": "msat",
"description": [
"The maximum value which this channel could pass. This or *minimum_msat* must be specified, but not both."
]
},
"minimum_msat": {
"type": "msat",
"description": [
"The minumum value which this channel could pass. This or *minimum_msat* must be specified, but not both."
]
},
"maximum_msat": {
"type": "msat",
"description": [
"The maximum value which this channel could pass. This or *minimum_msat* must be specified, but not both."
]
}
}
},