UI test for change password

Help docs

frontend/src/locale/src/HelpDoc/en/Certificates.md

@@ -2,11 +2,25 @@
 
 ## HTTP Certificate
 
-todo
+A HTTP validated certificate means that the Certificate Authority (CA) will
+attempt to reach your domains over HTTP (not HTTPS!) and if successful, the CA
+will issue your certificate.
+
+For this method, you will have to have a _Host_ created for your domains(s) that
+is accessible with HTTP. After a certificate has been given, you can modify the
+_Host_ to also use this certificate for HTTPS connections. However, the _Host_
+will still need to be configured for HTTP access in order for the certificate to
+renew.
 
 ## DNS Certificate
 
-todo
+A DNS validated certificate requires you to create a DNS Provider. This DNS
+Provider will be used to create temporary records on your domain and then the CA
+will query those records to be sure you're the owner and if successful, the CA
+will issue your certificate.
+
+You do not need a _Host_ to be created prior to requesting this type of
+certificate. Nor do you need to have your _Host_ configured for HTTP access.
 
 ## Custom Certificate
 
@@ -15,3 +29,7 @@ todo
 ## MKCert Certificate
 
 todo
+
+## Choosing a Certificate Authority
+
+If you're not sure, use **ZeroSSL.**

frontend/src/locale/src/HelpDoc/en/DNSProviders.md

@@ -1,3 +1,14 @@
 # DNS Providers Help
 
-todo
+A DNS Provider is a service that hosts your domain(s) and this will be
+specifically used when requesting new _Certificates_ via DNS Validation.
+
+It is preferred to use DNS Validation, so check if your domain is hosted with
+one of the supported Acme.sh providers:
+
+- [DNS Page 1](https://github.com/acmesh-official/acme.sh/wiki/dnsapi)
+- [DNS Page 2](https://github.com/acmesh-official/acme.sh/wiki/dnsapi2)
+
+Should your DNS Provider be supported by Acme.sh and not available in this
+project, please
+[open an issue on Github](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/new/choose).