Merge branch 'dev' of github.com:babylonlabs-io/babylon into rafilx/e…

…2e-upgrade-btc-headers

.github/workflows/ci.yml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   lint_test:
-    uses: babylonchain/.github/.github/workflows/reusable_go_lint_test.yml@v0.1.0
+    uses: babylonlabs-io/.github/.github/workflows/reusable_go_lint_test.yml@v0.2.1
     with:
       run-unit-tests: true
       run-integration-tests: true
@@ -16,7 +16,7 @@ jobs:
         sudo make test-e2e
 
   docker_pipeline:
-    uses: babylonchain/.github/.github/workflows/reusable_docker_pipeline.yml@v0.1.0
+    uses: babylonlabs-io/.github/.github/workflows/reusable_docker_pipeline.yml@v0.2.1
     secrets: inherit
     with:
      publish: false

docs/transaction-impl-spec.md

@@ -159,7 +159,7 @@ member required to authorize spending using `unbonding_script` or `slashing_scri
 - `staking_amout` - chosen by the user, it will be placed in `staking_output.value`
 - `btc_network` - btc network on which staking transactions will take place
 
-#### Building OP_RETRUN and staking output implementation
+#### Building OP_RETURN and staking output implementation
 
 The Babylon staking library exposes the [BuildV0IdentifiableStakingOutputsAndTx](../btcstaking/identifiable_staking.go?plain=1#L231)
 function with the following signature:
@@ -324,7 +324,7 @@ import (
 	"github.com/btcsuite/btcd/btcutil/psbt"
 )
 
-func BuildPsbtForSigningUnbondingTransaciton(
+func BuildPsbtForSigningUnbondingTransaction(
 	unbondingTx *wire.MsgTx,
 	stakingOutput *wire.TxOut,
 	stakerKey *btcec.PublicKey,

x/finality/README.md

@@ -2,7 +2,7 @@
 
 Babylon's BTC Staking protocol introduces an additional consensus round on
 blocks produced by CometBFT, called the finality round. The participants of this
-round are referred as finality providers and their voting power stems from
+round are referred to as finality providers and their voting power stems from
 staked bitcoins delegated to them.
 
 The Finality module is responsible for handling finality votes, maintaining the
@@ -12,7 +12,7 @@ in the finalization rounds. This includes:
 - handling requests for submitting finality votes from finality providers;
 - maintaining the finalization status of blocks;
 - identifying sluggish finality providers; and
-- maintaining equivocation evidences of culpable finality providers.
+- maintaining equivocation evidence of culpable finality providers.
 
 ## Table of contents