Skip to content

Commit a00c357

Browse files
committed
Merge #615: Fix typo in RBF FAQ post
5fff343 Fix typo in RBF FAQ post (Sev) Pull request description: Tree-SHA512: ef4aede47cf12426cc304704f4e982aba6ea7c3969b49fb846119781d94e69f7d5b1b45103a89b4861de352b81bf01a68d8424469d10798497d4c520646ff8d5
2 parents a055370 + 5fff343 commit a00c357

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/en/pages/faq/2016-01-21-rbf-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ Bitcoin Core 0.12 will be released around February 2016 and will include opt-in
8989

9090
## Is opt-in RBF only useful for adjusting fees?
9191

92-
No, another useful thing wallets can do with opt-in RBF is combine two or payments into a single payment when the first payment hasn't confirmed yet. This can save a large number of bytes and transaction fees even though the replacement will have pay a higher fee than the original.
92+
No, another useful thing wallets can do with opt-in RBF is combine two or more payments into a single payment when the first payment hasn't confirmed yet. This can save a large number of bytes and transaction fees even though the replacement will have to pay a higher fee than the original.
9393

9494
Opt-in RBF can also be used to implement more advanced cooperative stability schemes such as [transaction cut-through](https://bitcointalk.org/index.php?topic=281848.0).
9595

0 commit comments

Comments
 (0)