From f45d7c578481540fd88436a53b4123e332355ded Mon Sep 17 00:00:00 2001
From: kiminuo <58662979+kiminuo@users.noreply.github.com>
Date: Wed, 31 Mar 2021 10:22:39 +0200
Subject: Update bip-0174.mediawiki

I, personally, find this easier to read.
---
 bip-0174.mediawiki | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

(limited to 'bip-0174.mediawiki')

diff --git a/bip-0174.mediawiki b/bip-0174.mediawiki
index 75fea0e..56d9cdb 100644
--- a/bip-0174.mediawiki
+++ b/bip-0174.mediawiki
@@ -74,13 +74,11 @@ Where:
 : Magic bytes which are ASCII for psbt <ref>'''Why use 4 bytes for psbt?''' The
 transaction format needed to start with a 5 byte header which uniquely identifies
 it. The first bytes were chosen to be the ASCII for psbt because that stands for
-Partially Signed Bitcoin Transaction. </ref> followed by a separator of <tt>0xFF</tt>
-<ref>'''Why Use a separator after the magic bytes?''' The separator
+Partially Signed Bitcoin Transaction. </ref> followed by a separator of <tt>0xFF</tt><ref>'''Why Use a separator after the magic bytes?''' The separator
 is part of the 5 byte header for PSBT. This byte is a separator of <tt>0xff</tt> because
 this will cause any non-PSBT unserializer to fail to properly unserialize the PSBT
 as a normal transaction. Likewise, since the 5 byte header is fixed, no transaction
-in the non-PSBT format will be able to be unserialized by a PSBT unserializer.</ref>. This integer must be serialized
-in most significant byte order.
+in the non-PSBT format will be able to be unserialized by a PSBT unserializer.</ref>. This integer must be serialized in most significant byte order.
 
 The currently defined global types are as follows:
 
-- 
cgit v1.2.3

