qc2 check1

author_bio.html

@@ -9,5 +9,5 @@
 
 <p>As a bitcoin entrepreneur, Andreas has founded a number of Bitcoin businesses and launched several community open source projects. He serves as an advisor to several bitcoin and cryptocurrency companies. He is a widely published author of articles and blog posts on bitcoin, a permanent host on the popular Let’s Talk Bitcoin podcast, and a frequent speaker at technology and security conferences worldwide.</p>
 
-<p><strong>David A. Harding</strong> is a technical writer focused on creating documentation for open source software. He is the coauthor of the Bitcoin Optech weekly newsletter (2018–2023), 21.co Bitcoin Computer tutorials (2015–2017), and Bitcoin.org developer documentation (2014–2015). He is also a Brink.dev grant committee member (2022–2023) and former board member (2020–2022).</p>
+<p><strong>David A. Harding</strong> is a technical writer focused on creating documentation for open source software. He is the coauthor of the Bitcoin Optech weekly newsletter <span class='keep-together'>(2018–2023),</span> 21.co Bitcoin Computer tutorials (2015–2017), and Bitcoin.org developer documentation (2014–2015). He is also a Brink.dev grant committee member (2022–2023) and former board member (2020–2022).</p>
 </section>

ch03_bitcoin-core.adoc

@@ -976,7 +976,7 @@ will demonstrate accessing Bitcoin Core from another program.
 
 Bitcoin Core's API is a JSON-RPC interface. JSON is a very convenient way to present data that
 both humans and programs can easily read. RPC stands for remote
-procedure call, which means that we are calling procedures (functions)
+[.keep-together]#procedure# call, which means that we are calling procedures (functions)
 that are remote (on the Bitcoin Core node) via a network protocol. In
 this case, the network protocol is HTTP.
 

ch04_keys.adoc

@@ -1337,16 +1337,19 @@ digest of that function in the witness program.  For P2SH, the SHA256
 digest was hashed again with RIPEMD-160, but that may not be secure in
 some cases; for details, see <<p2sh_collision_attacks>>.  A result of
 using SHA256 without RIPEMD-160 is that P2WSH commitments are 32 bytes
-(256 bits) instead 20 bytes (160 bits).
+(256 bits) instead of 20 bytes (160 bits).
 
 For the pay-to-taproot (P2TR) output, the witness program is a point on
 the secp256k1 curve.  It may be a simple public key, but in most cases
 it should be a public key that commits to some additional data.  We'll
 learn more about that commitment in <<taproot>>.
 
+++++
+<p class="fix_tracking2">
 For the example of a future segwit version, we simply use the highest
 possible segwit version number (16) and the smallest allowed witness
-program (2 bytes) with a null value.
+program (2 bytes) with a null value.</p>
+++++
 
 Now that we know the version number and the witness program, we can
 convert each of them into a bech32 address.  Let's use the bech32m reference

ch07_authorization-authentication.adoc

@@ -1184,7 +1184,7 @@ account directly after he gains access to the capital account's
 transaction records.
 
 <<variable_timelock_multisig>> is the redeem script that Mohammed designs to achieve this (line
-number have been prefixed).
+numbers have been prefixed).
 
 [[variable_timelock_multisig]]
 .Variable multi-signature with timelock

ch10_network.adoc

@@ -1199,6 +1199,7 @@ You can find more instructions on running Bitcoin Core as a Tor hidden
 service in the Bitcoin Core documentation (_docs/tor.md_) and various
 online tutorials.
 
+[role="less_space pagebreak-before"]
 [[mempool]]
 === Mempools and Orphan Pools
 

ch11_blockchain.adoc

@@ -826,7 +826,7 @@ Bitcoin's ((("blockchain", "test blockchains", "development usage")))((("test bl
 blockchains (regtest, signet, testnet3, mainnet) offer a range
 of testing environments for bitcoin development. Use the test
 blockchains whether you are developing for Bitcoin Core or another
-full-node consensus client; an application such as a wallet, exchange,
+full-node consensus client; developing an application such as a wallet, exchange,
 ecommerce site; or even developing novel smart contracts and complex
 scripts).