Change default branch references from master to main (#113)

.github/workflows/deploy.yml

@@ -2,7 +2,7 @@ name: Deploy
 on:
   push:
     branches:
-      - master
+      - main
 
 jobs:
   deploy:

src/nakamoto-signer-developer-guide.md

@@ -39,10 +39,10 @@ cd stacks-blockchain/stacks-signer
 3. Checkout the appropriate release branch you wish to use if you are not using the default main branch
 
 ```console
-git checkout master
+git checkout main
 ```
 
-4. Compile the signer binary:  
+4. Compile the signer binary:
    Note the binary path defaults to `target/release/stacks-signer`.
 
 ```console

src/sbtc-releases/sbtc-dev.md

@@ -26,7 +26,7 @@ graph TD;
 
 ## sBTC Developer release reference implementation plan
 
-The reference implementation of the sBTC developer release, codenamed Alpha Romeo, is currently under implementation in [this repository](https://github.com/stacks-network/sbtc/tree/master/romeo).
+The reference implementation of the sBTC developer release, codenamed Alpha Romeo, is currently under implementation in [this repository](https://github.com/stacks-network/sbtc/tree/main/romeo).
 Every piece of functionality that is being worked on is formulated as [issues](https://github.com/stacks-network/sbtc/issues) with the [sBTC DR] prefix and `alpha-romeo` label.
 
 For anyone interested in tracking the high-level progress of the Alpha Romeo work, these key issues should provide a good view in how things are progressing.

src/sbtc-roadmap.md

@@ -40,7 +40,7 @@ gantt
     sBTC Releases              : doc3, after doc1, 2w
     sBTC Developer guides      : doc4, after doc2, 4w
     sBTC Nakamoto              : doc5, 2023-12-01, 8w
-  
+
 ```
 
 Each effort in the roadmap represents a key aspect of our development process. The following sections provide more detail about what we aim to achieve with each effort.