fix(ui): correct wording for channel open/close error

LN-Zap · May 10, 2020 · 626ba70 · 626ba70
1 parent c278f3a
commit 626ba70
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/renderer/reducers/channels/reducer.js b/renderer/reducers/channels/reducer.js
@@ -375,7 +375,7 @@ export const pushchannelerror = ({ nodePubkey, error }) => dispatch => {
       { payload: { pubkey: nodePubkey } },
       {
         variant: 'error',
-        message: `Unable to open channel: ${error}`,
+        message: error,
         isProcessing: false,
       }
     )
@@ -440,7 +440,7 @@ export const openChannel = data => async (dispatch, getState) => {
   } catch (e) {
     dispatch(
       pushchannelerror({
-        error: e.message,
+        error: `Unable to open channel: ${e.message}`,
         nodePubkey: e.payload.nodePubkey,
       })
     )
@@ -462,7 +462,7 @@ export const closeChannel = () => async (dispatch, getState) => {
 
     const [fundingTxid, outputIndex] = channelPoint.split(':')
 
-    // Attempt to open the channel.
+    // Attempt to close the channel.
     try {
       const data = await grpc.services.Lightning.closeChannel({
         channelPoint: {
@@ -476,7 +476,7 @@ export const closeChannel = () => async (dispatch, getState) => {
     } catch (e) {
       dispatch(
         pushchannelerror({
-          error: e.message,
+          error: `Unable to close channel: ${e.message}`,
           nodePubkey: e.payload.nodePubkey,
         })
       )