diff --git a/docs/tutorials/building-a-node-with-ldk/opening-a-channel.md b/docs/tutorials/building-a-node-with-ldk/opening-a-channel.md index 8d138329c..663d8b8cb 100644 --- a/docs/tutorials/building-a-node-with-ldk/opening-a-channel.md +++ b/docs/tutorials/building-a-node-with-ldk/opening-a-channel.md @@ -68,9 +68,9 @@ userConfig.setChannelHandshakeConfig(val: channelConfig) let createChannelResults = channelManager.createChannel( theirNetworkKey: pubKey, - channelValueSatoshis: amount, - pushMsat: pushMsat, - userChannelId: userId, + channelValueSatoshis: amount, + pushMsat: pushMsat, + userChannelId: userId, overrideConfig: userConfig ) ``` @@ -81,11 +81,11 @@ let createChannelResults = channelManager.createChannel( # FundingGenerationReady Event Handling -At this point, an outbound channel has been initiated with your peer and it will appear in `ChannelManager::list_channels`. However, the channel is not yet funded. Once your peer accepts the channel, you will be notified with a `FundingGenerationReady` event. It's then your responsibility to construct the funding transaction and pass it to ChannelManager, which will broadcast it once it receives your channel counterparty's signature. +At this point, an outbound channel has been initiated with your peer and it will appear in `ChannelManager::list_channels`. However, the channel is not yet funded. Once your peer accepts the channel, you will be notified with a `FundingGenerationReady` event. It's then your responsibility to construct the funding transaction and pass it to ChannelManager, which will broadcast it once it receives your channel counterparty's signature. ::: tip Note -Remember that the funding transaction must only spend SegWit inputs. +Remember that the funding transaction must only spend [SegWit](https://bitcoinops.org/en/topics/segregated-witness/) inputs. ::: @@ -93,7 +93,8 @@ Remember that the funding transaction must only spend SegWit inputs.