table test

ch01_intro.adoc

@@ -284,7 +284,6 @@ examples.
 
 [[recovery_code_sample]]
 .Sample recovery codes
-[cols="1,1"]
 |===
 | Wallet | Recovery code
 

ch03_bitcoin-core.adoc

@@ -477,39 +477,39 @@ Here are some of
 the most important options that you can set in the configuration file,
 or as command-line parameters to +bitcoind+:
 
-alertnotify:: Run a specified command or script to send emergency alerts
+++alertnotify++:: Run a specified command or script to send emergency alerts
 to the owner of this node.
 
-conf:: An alternative location for the configuration file. This only
+++conf++:: An alternative location for the configuration file. This only
 makes sense as a command-line parameter to +bitcoind+, as it can't be
 inside the configuration file it refers to.
 
-datadir:: Select the directory and filesystem in which to put all the
+++datadir++:: Select the directory and filesystem in which to put all the
 blockchain data. By default this is the _.bitcoin_ subdirectory of your
 home directory. Depending on your configuration, this can use from about 10
 gigabytes to almost 1 terabyte as of this writing, with the maximum size
 expected to increase by several hundred gigabytes per year.
 
-prune:: Reduce the blockchain disk space requirements to this many megabytes, by
+++prune++:: Reduce the blockchain disk space requirements to this many megabytes, by
 deleting old blocks. Use this on a resource-constrained node that can't
 fit the full blockchain.  Other parts of the system will use other disk
 space that can't currently be pruned, so you will still need at least
 the minimum amount of space mentioned in the +datadir+ option.
 
-txindex:: Maintain an index of all transactions. This allows you to
+++txindex++:: Maintain an index of all transactions. This allows you to
 programmatically retrieve any transaction by its ID provided that the
 block containing that transaction hasn't been pruned.
 
-dbcache:: The size of the UTXO cache. The default is 450 MiB. Increase
+++dbcache++:: The size of the UTXO cache. The default is 450 MiB. Increase
 this size on high-end hardware to read and write from your disk less
 often, or reduce the size on low-end hardware to save memory at the
 expense of using your disk more frequently.
 
-blocksonly:: Minimize your bandwidth usage by only accepting blocks of
+++blocksonly++:: Minimize your bandwidth usage by only accepting blocks of
 confirmed transactions from your peers instead of relaying unconfirmed
 transactions.
 
-maxmempool:: Limit the transaction memory pool to this many megabytes.
+++maxmempool++:: Limit the transaction memory pool to this many megabytes.
 Use it to reduce memory use on memory-constrained nodes.
 
 [[txindex]]

ch10_network.adoc

@@ -918,6 +918,7 @@ small differences are much more likely to occur than the large
 differences:
 
 [cols="1,1"]
+[options="header"]
 |===
 | Difference | Occurrences
 | 0 | 6

preface.asciidoc

@@ -59,7 +59,7 @@ All the code snippets use real values and calculations where possible, so that y
 
 === Using Code Examples
 
-This book is here to help you get your job done. In general, if example code is offered with this book, you may use it in your programs and documentation. You do not need to contact us for permission unless you’re reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O’Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product’s documentation does require permission.
+This book is here to help you get your job done. In general, if example code is offered with this book, you may use it in your programs and documentation. You do not need to contact us for permission unless you’re reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing examples from O’Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product’s documentation does require permission.
 
 We appreciate, but do not require, attribution. An attribution usually includes [.keep-together]#the title,# author, publisher, and ISBN. For example: “_Mastering Bitcoin_ by [.keep-together]#Andreas M.# Antonopoulos and David A. Harding (O’Reilly). Copyright 2024, ISBN 978-1-491-95438-6.”
 
@@ -82,6 +82,7 @@ However, note that the private keys used to construct addresses are either print
 DO NOT SEND MONEY TO ANY OF THE ADDRESSES IN THIS BOOK. Your money will be taken by another reader, or lost forever.
 ====
 
+=== O'Reilly Online Learning
 [role = "ormenabled"]
 [NOTE]
 ====
@@ -115,11 +116,11 @@ We have a web page for this book, where we list errata, examples, and any additi
 
 For news and information about our books and courses, visit link:$$https://oreilly.com$$[].
 
-Find us on LinkedIn: link:$$https://linkedin.com/company/oreilly-media$$[]
+Find us on LinkedIn: link:$$https://linkedin.com/company/oreilly-media$$[].
 
-Follow us on Twitter: link:$$https://twitter.com/oreillymedia$$[]
+Follow us on Twitter: link:$$https://twitter.com/oreillymedia$$[].
 
-Watch us on YouTube: link:$$https://youtube.com/oreillymedia$$[]
+Watch us on YouTube: link:$$https://youtube.com/oreillymedia$$[].
 
 
 === Contacting the Authors