diff --git a/doc/source/security/kubernetes/enable-https-access-for-starlingx-rest-and-web-server-endpoints.rst b/doc/source/security/kubernetes/enable-https-access-for-starlingx-rest-and-web-server-endpoints.rst
index 45d303aee..c694ac4de 100644
--- a/doc/source/security/kubernetes/enable-https-access-for-starlingx-rest-and-web-server-endpoints.rst
+++ b/doc/source/security/kubernetes/enable-https-access-for-starlingx-rest-and-web-server-endpoints.rst
@@ -28,8 +28,19 @@ When secure HTTPS connectivity is enabled, HTTP is disabled.
         changes to be displayed accurately in Horizon.
 
 
-Moving forward, the system will be have HTTPS enabled by default, as the REST
+Moving forward, the system will have HTTPS enabled by default, as the REST
 API & Web Server certificate will be issued from bootstrap using the Platform
 Issuer (``system-local-ca``). This certificate will be renewed by cert-manager,
 and can be updated using procedure in
-:ref:`migrate-platform-certificates-to-use-cert-manager-c0b1727e4e5d`.
\ No newline at end of file
+:ref:`migrate-platform-certificates-to-use-cert-manager-c0b1727e4e5d`.
+
+.. note::
+    
+    Disabling HTTPS should be limited to strictly necessary situations, and the
+    usage should be considered deprecated. The following commands can be used
+    to modify the HTTPS enabled configuration:
+
+    .. code-block:: none
+
+        system modify -p true|false
+        system modify --https_enabled true|false 
\ No newline at end of file