diff --git a/pentesting/5985-5986-pentesting-winrm.md b/pentesting/5985-5986-pentesting-winrm.md
index 986413ae5..1f4713085 100644
--- a/pentesting/5985-5986-pentesting-winrm.md
+++ b/pentesting/5985-5986-pentesting-winrm.md
@@ -7,14 +7,14 @@ description: >-
 
 ## WinRM
 
-[Windows Remote Management](https://msdn.microsoft.com/en-us/library/windows/desktop/aa384426%28v=vs.85%29.aspx) \(WinRM\) is a Microsoft protocol that allows remote management of Windows machines over HTTP\(S\) using SOAP. On the backend it's utilizing WMI, so you can think of it as an HTTP based API for WMI.
+[Windows Remote Management](https://msdn.microsoft.com/en-us/library/windows/desktop/aa384426%28v=vs.85%29.aspx) \(WinRM\) is a Microsoft protocol that **allows remote management of Windows machines** over HTTP\(S\) using SOAP. On the backend it's utilising WMI, so you can think of it as an HTTP based API for WMI.
 
 If WinRM is enabled on the machine, it's trivial to remotely administer the machine from PowerShell. In fact, you can just drop in to a remote PowerShell session on the machine \(as if you were using SSH!\)
 
 The easiest way to detect whether WinRM is available is by seeing if the port is opened. WinRM will listen on one of two ports:
 
-* 5985/tcp \(HTTP\)
-* 5986/tcp \(HTTPS\)
+* **5985/tcp \(HTTP\)**
+* **5986/tcp \(HTTPS\)**
 
 If one of these ports is open, WinRM is configured and you can try entering a remote session.