diff --git a/TypeScript/10ScopesAndTypes/README.md b/TypeScript/10ScopesAndTypes/README.md index 678c9d3..434d063 100644 --- a/TypeScript/10ScopesAndTypes/README.md +++ b/TypeScript/10ScopesAndTypes/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/11BundleLoadingSample/README.md b/TypeScript/11BundleLoadingSample/README.md index 678c9d3..434d063 100644 --- a/TypeScript/11BundleLoadingSample/README.md +++ b/TypeScript/11BundleLoadingSample/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/12ClassExtensionOverride/README.md b/TypeScript/12ClassExtensionOverride/README.md index 678c9d3..434d063 100644 --- a/TypeScript/12ClassExtensionOverride/README.md +++ b/TypeScript/12ClassExtensionOverride/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/13AddTrader/README.md b/TypeScript/13AddTrader/README.md index 678c9d3..434d063 100644 --- a/TypeScript/13AddTrader/README.md +++ b/TypeScript/13AddTrader/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/14AfterDBLoadHook/README.md b/TypeScript/14AfterDBLoadHook/README.md index 678c9d3..434d063 100644 --- a/TypeScript/14AfterDBLoadHook/README.md +++ b/TypeScript/14AfterDBLoadHook/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/15HttpListenerExample/README.md b/TypeScript/15HttpListenerExample/README.md index 678c9d3..434d063 100644 --- a/TypeScript/15HttpListenerExample/README.md +++ b/TypeScript/15HttpListenerExample/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/16ImporterUtil/README.md b/TypeScript/16ImporterUtil/README.md index 678c9d3..434d063 100644 --- a/TypeScript/16ImporterUtil/README.md +++ b/TypeScript/16ImporterUtil/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/17AsyncImporterWithDependency1/README.md b/TypeScript/17AsyncImporterWithDependency1/README.md index 678c9d3..434d063 100644 --- a/TypeScript/17AsyncImporterWithDependency1/README.md +++ b/TypeScript/17AsyncImporterWithDependency1/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/17AsyncImporterWithDependency2/README.md b/TypeScript/17AsyncImporterWithDependency2/README.md index 678c9d3..434d063 100644 --- a/TypeScript/17AsyncImporterWithDependency2/README.md +++ b/TypeScript/17AsyncImporterWithDependency2/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/18CustomItemService/README.md b/TypeScript/18CustomItemService/README.md index 678c9d3..434d063 100644 --- a/TypeScript/18CustomItemService/README.md +++ b/TypeScript/18CustomItemService/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/1LogToConsole/README.md b/TypeScript/1LogToConsole/README.md index 678c9d3..434d063 100644 --- a/TypeScript/1LogToConsole/README.md +++ b/TypeScript/1LogToConsole/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/2EditDatabase/README.md b/TypeScript/2EditDatabase/README.md index 678c9d3..434d063 100644 --- a/TypeScript/2EditDatabase/README.md +++ b/TypeScript/2EditDatabase/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/3GetSptConfigFile/README.md b/TypeScript/3GetSptConfigFile/README.md index 678c9d3..434d063 100644 --- a/TypeScript/3GetSptConfigFile/README.md +++ b/TypeScript/3GetSptConfigFile/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/4UseACustomConfigFile/README.md b/TypeScript/4UseACustomConfigFile/README.md index 678c9d3..434d063 100644 --- a/TypeScript/4UseACustomConfigFile/README.md +++ b/TypeScript/4UseACustomConfigFile/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/5ReplaceMethod/README.md b/TypeScript/5ReplaceMethod/README.md index 678c9d3..434d063 100644 --- a/TypeScript/5ReplaceMethod/README.md +++ b/TypeScript/5ReplaceMethod/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/6ReferenceAnotherClass/README.md b/TypeScript/6ReferenceAnotherClass/README.md index 678c9d3..434d063 100644 --- a/TypeScript/6ReferenceAnotherClass/README.md +++ b/TypeScript/6ReferenceAnotherClass/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/7OnLoadHook/README.md b/TypeScript/7OnLoadHook/README.md index 678c9d3..434d063 100644 --- a/TypeScript/7OnLoadHook/README.md +++ b/TypeScript/7OnLoadHook/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/8OnUpdateHook/README.md b/TypeScript/8OnUpdateHook/README.md index 678c9d3..434d063 100644 --- a/TypeScript/8OnUpdateHook/README.md +++ b/TypeScript/8OnUpdateHook/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:** diff --git a/TypeScript/9RouterHooks/README.md b/TypeScript/9RouterHooks/README.md index 678c9d3..434d063 100644 --- a/TypeScript/9RouterHooks/README.md +++ b/TypeScript/9RouterHooks/README.md @@ -15,15 +15,15 @@ A system reboot may be needed after install. The second step is having an IDE ready. We've setup a VSCodium workspace file to help with this. -You CAN use Visual Studio Code if you so desire, just keep in mind that our dev tests on the mod files was done using VSCode. +You CAN use Visual Studio Code if you so desire, just keep in mind that our devs tests on the mod files was done using VSCode. -You can get VSCOde here: https://code.visualstudio.com/ +You can get VSCode here: https://code.visualstudio.com/ ## **Workspace:** -Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCodium (File->Open Workspace from File...). +Once you have NodeJS and VSCode/VSCodium ready, open the mod.code-workspace file with VSCode (File->Open Workspace from File...). -Once the project loads into VSCodium you will be recommended to install the ESLint plugin. This is HIGHLY recommended. +Once the project loads you may be recommended to install the ESLint plugin. This is HIGHLY recommended. ## **Environment Setup:**