diff --git a/README.MD b/README.MD
index 016f301..615221a 100644
--- a/README.MD
+++ b/README.MD
@@ -1,3 +1,5 @@
+[![Documentation Status](https://readthedocs.org/projects/powerful-computer-manager/badge/?version=latest)](https://powerful-computer-manager.readthedocs.io/es/latest/?badge=latest)
+
 # What is "Powerful Computer Manager"?
 Powerful Computer Manager is the super-simple-but-powerful program to automatizate tasks in groups of computers (In a Active Directory site, or not) in a unattended way.
 It inteed to be a simple SSMS alternative, that inventarizes computers and install/remove software in it, tweak system of run arbitrary commands.
@@ -11,4 +13,6 @@ I'm using this program in the company I work with 12 computers with Windows 8.1/
 
 It's not error proof, then, I don't have any responsability if something crashes, but you can open a Issue and will see it
 
-Please open docs/index.md to read the rest
+# Documentation 
+
+Please open docs/index.md or [Online ReadTheDocs Documentation](https://powerful-computer-manager.readthedocs.io/es/latest/?badge=latest) to read the documentation online
diff --git a/docs/index.md b/docs/index.md
index 2aa9361..9a0e80a 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -34,7 +34,7 @@ For server you can use Linux or Windows, and in theory any environment that can
 ## Clients
 -	Windows:
 	-	Windows 7 SP1 absolute minimal, but its only officially tested in 8.1 and 10, Windows 7 is being old now.
-	-	It needs Powershell 5.0+ (Not PWCore versions), lower versions doesnt guaranteed to work, not tested. In Windows 7 and 8.1, you have to update Powershell. (With Powershell 3.0/4.0, some commands like Get-Package doesn't work)
+	-	It needs Powershell 5.0+ (Or Powershell Core 6.1+), lower versions doesnt guaranteed to work, not tested. In Windows 7 and 8.1, you have to update Powershell. (With Powershell 3.0/4.0, some commands like Get-Package doesn't work)
 		You can update from here: https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-windows-powershell?view=powershell-6#upgrading-existing-windows-powershell (Download link: https://www.microsoft.com/en-us/download/details.aspx?id=54616)
 
 -	Linux:
@@ -56,11 +56,11 @@ For server you can use Linux or Windows, and in theory any environment that can
 	- resources=\\XX -> UNC/Path where software are. When you write cooks, you will do come "REPOTOLOCAL|somefile.msi", well, this folder is where it will copy files. It has be readable by clients.
 -   For clients to work, they have to run "client\client.ps1" every 30 mins/1 hour or so, I did using Active Directory and a Task Scheduled GPO (Copying client.ps1 and configpcm.ini files from Client to SysVol\DomainName\Scripts\)
     - User: SYSTEM    (Or NT\SYSTEM)
-    - Command: powershell.exe
+    - Command: powershell.exe   (Or pwsh.exe if using Powershell Core)
     - Args: -executionpolicy bypass -windowstyle hidden -noninteractive -nologo -file "\\SERVER\SysVol\DOMAINNAME\scripts\client.ps1"
 	
 	Note: client.ps1 has to have controlpcm.ini file with it and has to be readable and executable by clients
--	If you don't have Active Directory, you can do the Task Scheduled task in every computer without problems, and using another Shared folder, it will work right.
+-	If you don't have Active Directory, you can do the Task Scheduled task in every computer without problems, and using any Shared folder, it will work right.
 
 -   For use of param "-startup 1" for cooks that has to be run without users, you will have to create a Task Scheduled GPO when workstation startsup/powers off with param -startup 1, like:
 	- Args: -executionpolicy bypass -windowstyle hidden -noninteractive -nologo -file "\\SERVER\SysVol\DOMAINNAME\scripts\client.ps1" -startup 1