Merge commit '03f6867755c246cf4ea64b9d85134558ce06b9b5' into dev

* commit '03f6867755c246cf4ea64b9d85134558ce06b9b5':
  `OP_PUSH` instead of `OP_1` in inscription docs (ordinals#2135)
  Fix typo in Sparrow Wallet docs (ordinals#2077)

docs/src/guides/collecting/sparrow-wallet.md

@@ -48,7 +48,7 @@ You now have a wallet which is compatible with `ord`, and can be imported into `
 
 Each time you want to receive you should use a brand-new address, and not re-use existing addresses.
 
-Note that bitcoin is different to some other blockchain wallets, in that this wallet can generate an unlimited number of new addreses. You can generate a new address by clicking on the `Get Next Address` button. You can see all of your addresses in the `Addresses` tab of the app.
+Note that bitcoin is different to some other blockchain wallets, in that this wallet can generate an unlimited number of new addresses. You can generate a new address by clicking on the `Get Next Address` button. You can see all of your addresses in the `Addresses` tab of the app.
 
 You can add a label to each address, so you can keep track of what it was used for.
 

docs/src/inscriptions.md

@@ -43,18 +43,18 @@ follows:
 OP_FALSE
 OP_IF
   OP_PUSH "ord"
-  OP_1
+  OP_PUSH 1
   OP_PUSH "text/plain;charset=utf-8"
-  OP_0
+  OP_PUSH 0
   OP_PUSH "Hello, world!"
 OP_ENDIF
 ```
 
 First the string `ord` is pushed, to disambiguate inscriptions from other uses
 of envelopes.
 
-`OP_1` indicates that the next push contains the content type, and `OP_0`
-indicates that subsequent data pushes contain the content itself. Multiple data
+`OP_PUSH 1` indicates that the next push contains the content type, and `OP_PUSH
+0`indicates that subsequent data pushes contain the content itself. Multiple data
 pushes must be used for large inscriptions, as one of taproot's few
 restrictions is that individual data pushes may not be larger than 520 bytes.