Merge pull request CosmosOS#2310 from AsertCreator/master

Fix typo in new Plug docs and update userkit maker
TomLeeLive · Jun 21, 2022 · d64e68a · d64e68a
2 parents 758a457 + e3273c4
commit d64e68a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/Docs/articles/Kernel/Plugs.md b/Docs/articles/Kernel/Plugs.md
@@ -26,7 +26,7 @@ Plugs change what happens in step 2. A normal code plug means that rather taking
 
 # Implementing a Plug
 
-While one always plugs individual methods, plugs are defined class wise. Therefore the first step to plugging any method is to define a new static class to contain all the pluggged methods for some certain type. This class must be decorated with the `Plug` attribute. The plug attribute either takes the type it is plugging(`Plug(Tpe target)`) or a string with the target name(`Plug(string targetName)`). Using the string target name is required when plugging internal or private classes. An example for a plugged class is for the Math class. https://github.com/CosmosOS/Cosmos/blob/8a8393353f1957890c5154650e29847fd22bf893/source/Cosmos.System2_Plugs/System/MathImpl.cs#L8-L9
+While one always plugs individual methods, plugs are defined class wise. Therefore the first step to plugging any method is to define a new static class to contain all the pluggged methods for some certain type. This class must be decorated with the `Plug` attribute. The plug attribute either takes the type it is plugging(`Plug(Type target)`) or a string with the target name(`Plug(string targetName)`). Using the string target name is required when plugging internal or private classes. An example for a plugged class is for the Math class. https://github.com/CosmosOS/Cosmos/blob/8a8393353f1957890c5154650e29847fd22bf893/source/Cosmos.System2_Plugs/System/MathImpl.cs#L8-L9
 
 ## Code Plug
 

diff --git a/userkit install.bat b/userkit install.bat
@@ -1,3 +1,3 @@
 @echo off
 
-install-VS2019 -USERKIT %*
+install-VS2022 -USERKIT %*