fix: fix more edit paths

Author: hansemannn

README.md

@@ -4,7 +4,7 @@
 
 ## Getting started
 
-These docs aim to be a hybrid solution of Markdown bases guides and dynamically generated docs for API references using the existing [apidoc](https://github.com/tidev/titanium-sdk/tree/master/apidoc) from Titanium.
+These docs aim to be a hybrid solution of Markdown bases guides and dynamically generated docs for API references using the existing [apidoc](https://github.com/tidev/titanium-sdk/tree/main/apidoc) from Titanium.
 
 ### Installation
 
@@ -99,7 +99,7 @@ module.exports = {
 
 ### Adding API docs
 
-In theory the `api.json` contains all required information to automatically generate markdown files. However, some APIs contain very detailed description and various examples which are just better to maintain directly in markdown files here than in their `.yaml` counterpart in Titanium's [apidoc](https://github.com/tidev/titanium-sdk/tree/master/apidoc). All other information regarding the API for a type in Titanium is then taken from the `api.json`. This creates a clear seperation of extensive documentation and simple api reference.
+In theory the `api.json` contains all required information to automatically generate markdown files. However, some APIs contain very detailed description and various examples which are just better to maintain directly in markdown files here than in their `.yaml` counterpart in Titanium's [apidoc](https://github.com/tidev/titanium-sdk/tree/main/apidoc). All other information regarding the API for a type in Titanium is then taken from the `api.json`. This creates a clear seperation of extensive documentation and simple api reference.
 
 To automatically migrate a type over to these docs you can run the migration script.
 

docs/guide/Alloy_Framework/README.md

@@ -7,7 +7,7 @@ weight: '30'
 
 This documentation covers Alloy, an Appcelerator framework for the Titanium SDK designed to rapidly develop quality Titanium applications. It is based on the model-view-controller architecture and contains built-in support for [Backbone.js](http://docs.appcelerator.com/backbone/0.9.2/) and [Underscore.js](http://underscorejs.org/).
 
-Review the [Alloy Release Notes](https://github.com/tidev/alloy/blob/master/CHANGELOG.md) to see what has changed.
+Review the [Alloy Release Notes](https://github.com/tidev/alloy/blob/main/CHANGELOG.md) to see what has changed.
 
 ## Chapters
 

docs/guide/Titanium_SDK/Titanium_SDK_Getting_Started/Installation_and_Configuration/Titanium_Compatibility_Matrix/README.md

@@ -111,7 +111,7 @@ The _Android SDK Manager_ installer may be obtained from the [Android Studio and
 
 #### Required Android Packages
 
-As of **Titanium 9.0.0**, the build system will automatically download the Android SDK platforms and tools needed. For details look at the dependencies in the main Titanium SDK repository: https://github.com/tidev/titanium-sdk/blob/master/android/package.json#L19-L28
+As of **Titanium 9.0.0**, the build system will automatically download the Android SDK platforms and tools needed. For details look at the dependencies in the main Titanium SDK repository: https://github.com/tidev/titanium-sdk/blob/main/android/package.json#L19-L28
 
 ::: warning ⚠️ Warning
 Take caution before upgrading these packages, as changes to the way they work has broken the Titanium toolchain a number of times in the past. Although these problems are often beyond our control, we always do our utmost to fix them as soon as we are made aware of them.

docs/guide/Titanium_SDK/Titanium_SDK_Guide/Contributing_to_Titanium/Platform_Development/Building_the_Titanium_SDK_From_Source.md

@@ -110,7 +110,7 @@ git fetch upstream --prune
 
 ## Build the SDK
 
-The method written below is the old way. The repo has now been updated to do away with scons. Please refer to [https://github.com/tidev/titanium\_mobile/blob/master/README.md#building-locally](https://github.com/tidev/titanium-sdk/blob/master/README.md#building-locally) on how to build locally with Node.JS scrips.
+The method written below is the old way. The repo has now been updated to do away with scons. Please refer to [https://github.com/tidev/titanium\_mobile/blob/master/README.md#building-locally](https://github.com/tidev/titanium-sdk/blob/main/README.md#building-locally) on how to build locally with Node.JS scrips.
 
 In the root of your `titanium_mobile` repo, run the following commands:
 

docs/guide/Titanium_SDK/Titanium_SDK_How-tos/Extending_Titanium_Mobile/Android_Module_Development_Guide/Android_Module_Project.md

@@ -210,7 +210,7 @@ try {
 
 The Titanium SDK uses clang-format to have a unified code-style in its source-code (clang-format for iOS and Android, ESLint for the CLI). You can do the same by following the following few steps:
 
-1. Copy the `.clang-format` file from [here](https://github.com/tidev/titanium-sdk/blob/master/android/.clang-format) to the "`android/`" directory of your module project, e.g. `<module-root>/ios/.clang-format`
+1. Copy the `.clang-format` file from [here](https://github.com/tidev/titanium-sdk/blob/main/android/.clang-format) to the "`android/`" directory of your module project, e.g. `<module-root>/ios/.clang-format`
 
 2. Install the [clang-format CLI](https://clang.llvm.org/docs/ClangFormat.html): `npm install -g clang-format`
 

docs/guide/Titanium_SDK/Titanium_SDK_How-tos/Extending_Titanium_Mobile/iOS_Module_Development_Guide/iOS_Module_Project.md

@@ -248,7 +248,7 @@ UIImage *image = [TiUtils image:url proxy:self];
 
 The Titanium SDK uses clang-format to have a unified code-style in its source-code (clang-format for iOS and Android, ESLint for the CLI). You can do the same by following the following few steps:
 
-1. Copy the `.clang-format` file from [here](https://github.com/tidev/titanium-sdk/blob/master/iphone/.clang-format) to the "`ios/`" directory of your module project, e.g. `<module-root>/ios/.clang-format`
+1. Copy the `.clang-format` file from [here](https://github.com/tidev/titanium-sdk/blob/main/iphone/.clang-format) to the "`ios/`" directory of your module project, e.g. `<module-root>/ios/.clang-format`
 
 2. Install the [clang-format CLI](https://clang.llvm.org/docs/ClangFormat.html): `npm install -g clang-format`
 

docs/guide/Titanium_SDK/Titanium_SDK_How-tos/User_Interface_Fundamentals/Icons_and_Splash_Screens/iOS_Launch_Files.md

@@ -67,7 +67,7 @@ This will also change the background color of your app between after the launch
 
 ### Option B: Use a custom Storyboard
 
-To use a custom Storyboard, put this file in [app/platform/ios/LaunchScreen.storyboard](https://github.com/tidev/titanium-sdk/blob/master/iphone/iphone/LaunchScreen.storyboard) (for Alloy projects) or [platform/ios/LaunchScreen.storyboard](https://github.com/tidev/titanium-sdk/blob/master/iphone/iphone/LaunchScreen.storyboard) (for classic projects). As you can see the sample has it disabled using a `_` prefix. Just remove the underscore and do a clean build to see the difference:
+To use a custom Storyboard, put this file in [app/platform/ios/LaunchScreen.storyboard](https://github.com/tidev/titanium-sdk/blob/main/iphone/iphone/LaunchScreen.storyboard) (for Alloy projects) or [platform/ios/LaunchScreen.storyboard](https://github.com/tidev/titanium-sdk/blob/main/iphone/iphone/LaunchScreen.storyboard) (for classic projects). As you can see the sample has it disabled using a `_` prefix. Just remove the underscore and do a clean build to see the difference:
 
 ![launch-custom](./launch-custom.png)
 

website/pages/tdoc-spec.md

@@ -13,7 +13,7 @@ The migration of this document is currently still a work in progress. For the or
 :::
 
 :::tip
-To see an example of this spec in use, check out the documentation for [Titanium](https://github.com/tidev/titanium-sdk/blob/master/apidoc/Titanium).
+To see an example of this spec in use, check out the documentation for [Titanium](https://github.com/tidev/titanium-sdk/blob/main/apidoc/Titanium).
 :::
 
 ## Overview