Replace master branch with main in documentations

Author: jzhou77

documentation/sphinx/source/architecture.rst

@@ -137,7 +137,7 @@ storage server is responsible for which data range, and ensures data is
 evenly distributed across all storage servers (SS). Data distributor as
 a singleton in the cluster is recruited and monitored by Cluster
 Controller. See `internal
-documentation <https://github.com/apple/foundationdb/blob/master/design/data-distributor-internals.md>`__.
+documentation <https://github.com/apple/foundationdb/blob/main/design/data-distributor-internals.md>`__.
 
 Ratekeeper
 ~~~~~~~~~~
@@ -313,7 +313,7 @@ Transaction Logs. After previous Log Servers are stopped and new transaction
 system is recruited, the Master writes the coordinated states with current
 transaction system information. Finally, the Master accepts new
 transaction commits. See details in this
-`documentation <https://github.com/apple/foundationdb/blob/master/design/recovery-internals.md>`__.
+`documentation <https://github.com/apple/foundationdb/blob/main/design/recovery-internals.md>`__.
 
 Because GRV Proxies, Commit Proxies and Resolvers are stateless, their 
 recoveries have no extra work. In contrast, Transaction Logs save the 
@@ -345,16 +345,16 @@ Resources
 Post <https://forums.foundationdb.org/t/technical-overview-of-the-database/135/26>`__
 
 `Existing Architecture
-Documentation <https://github.com/apple/foundationdb/blob/master/documentation/sphinx/source/kv-architecture.rst>`__
+Documentation <https://github.com/apple/foundationdb/blob/main/documentation/sphinx/source/kv-architecture.rst>`__
 
 `Summit
 Presentation <https://www.youtube.com/watch?list=PLbzoR-pLrL6q7uYN-94-p_-Q3hyAmpI7o&v=EMwhsGsxfPU&feature=emb_logo>`__
 
 `Data Distribution
-Documentation <https://github.com/apple/foundationdb/blob/master/design/data-distributor-internals.md>`__
+Documentation <https://github.com/apple/foundationdb/blob/main/design/data-distributor-internals.md>`__
 
 `Recovery
-Documentation <https://github.com/apple/foundationdb/blob/master/design/recovery-internals.md>`__
+Documentation <https://github.com/apple/foundationdb/blob/main/design/recovery-internals.md>`__
 
 .. |image0| image:: images/Architecture.png
 .. |image1| image:: images/architecture-1.jpeg

documentation/sphinx/source/release-notes/release-notes-700.rst

@@ -25,7 +25,7 @@ Features
 * Added TLS support to fdbdecode for decoding mutation log files stored in blobs. `(PR #4611) <https://github.com/apple/foundationdb/pull/4611>`_
 * Added ``initial_snapshot_interval`` to fdbbackup that can specify the duration of the first inconsistent snapshot written to the backup. `(PR #4620) <https://github.com/apple/foundationdb/pull/4620>`_
 * Added ``inconsistent_snapshot_only`` to fdbbackup that ignores mutation log files and only uses range files during the restore to speedup the process. `(PR #4704) <https://github.com/apple/foundationdb/pull/4704>`_
-* Added the Testing Storage Server (TSS), which allows FoundationDB to run an "untrusted" storage engine with identical workload to the current storage engine, with zero impact on durability or correctness, and minimal impact on performance. `(Documentation) <https://github.com/apple/foundationdb/blob/master/documentation/sphinx/source/tss.rst>`_ `(PR #4556) <https://github.com/apple/foundationdb/pull/4556>`_
+* Added the Testing Storage Server (TSS), which allows FoundationDB to run an "untrusted" storage engine with identical workload to the current storage engine, with zero impact on durability or correctness, and minimal impact on performance. `(Documentation) <https://github.com/apple/foundationdb/blob/main/documentation/sphinx/source/tss.rst>`_ `(PR #4556) <https://github.com/apple/foundationdb/pull/4556>`_
 * Added perpetual storage wiggle that supports less impactful B-trees recreation and data migration. These will also be used for deploying the Testing Storage Server which compares 2 storage engines' results. See :ref:`Documentation <perpetual-storage-wiggle>` for details. `(PR #4838) <https://github.com/apple/foundationdb/pull/4838>`_
 * Improved the efficiency with which storage servers replicate data between themselves. `(PR #5017) <https://github.com/apple/foundationdb/pull/5017>`_
 * Added support to ``exclude command`` to exclude based on locality match. `(PR #5113) <https://github.com/apple/foundationdb/pull/5113>`_

documentation/sphinx/source/transaction-profiler-analyzer.rst

@@ -18,7 +18,7 @@ The second part of transaction profiling involves deleting old sampled data to r
 
 There are many ways that this data can be exposed for analysis. One can imagine building a client that reads the data from the database and streams it to external tools such as Wavefront.
 
-One such tool that’s available as part of open source FDB is a python script called ``transaction_profiling_analyzer.py`` that's available here on `GitHUb <https://github.com/apple/foundationdb/blob/master/contrib/transaction_profiling_analyzer/transaction_profiling_analyzer.py>`_. It reads the sampled data from the database and outputs it in a user friendly format. Currently it’s most useful in identifying hot key-ranges (for both reading and writing).
+One such tool that’s available as part of open source FDB is a python script called ``transaction_profiling_analyzer.py`` that's available here on `GitHUb <https://github.com/apple/foundationdb/blob/main/contrib/transaction_profiling_analyzer/transaction_profiling_analyzer.py>`_. It reads the sampled data from the database and outputs it in a user friendly format. Currently it’s most useful in identifying hot key-ranges (for both reading and writing).
 
 Prerequisites
 =============