diff --git a/Servers & Workflows/Windows Server/SSL Certificates/Convert SSL Certificates into PFX Files.md b/Servers & Workflows/Windows Server/SSL Certificates/Convert SSL Certificates into PFX Files.md
index 078ec78..8c02382 100644
--- a/Servers & Workflows/Windows Server/SSL Certificates/Convert SSL Certificates into PFX Files.md	
+++ b/Servers & Workflows/Windows Server/SSL Certificates/Convert SSL Certificates into PFX Files.md	
@@ -11,13 +11,12 @@ private.key
 
 # Convert using OpenSSL
 You will need a linux machine such as Ubuntu 22.04LTS, or to download the Windows equivelant of OpenSSL in order to run the necessary commands to convert and package the files into a `.pfx` file that IIS Server Manager can use.
-:::note
+!!! note
 You need to make sure that all of the certificate files as well as private key are in the same folder (to keep things simple) during the conversion process.  **It will prompt you to enter a password for the PFX file, choose anything you want.**
-:::
+
 ```jsx title="OpenSSL Conversion Command"
 openssl pkcs12 -export -out IIS-Certificate.pfx -inkey private.key -in gd-g2_iis_intermediates.p7b -in certificate.crt
 ```
 
-:::tip
+!!! tip
 You can rename the files anything you want for organizational purposes.  Afterall, they are just plaintext files.  For example, you could rename `gd-g2_iis_intermediates.p7b` to `intermediate.bundle` and it would still work without issue in the command.  During the import phase in IIS Server Manager, you can check a box to enable Exporting the certificate, effectively reverse-engineering it back into a certificate and private key.
-:::
\ No newline at end of file