diff --git a/manual/setup/cluster_deploy_with_k8s.md b/manual/setup/cluster_deploy_with_k8s.md
index 68f6e1fb..953f2dbf 100644
--- a/manual/setup/cluster_deploy_with_k8s.md
+++ b/manual/setup/cluster_deploy_with_k8s.md
@@ -6,7 +6,7 @@ This manual explains how to deploy and run Seafile cluster on a Linux server usi
 
 ### System requirements
 
-In theory, you only need to prepare one node to deploy a cluster, but this does not conform to the K8S design concept, so we recommend that you prepare at least 3 nodes ():
+In theory, you only need to prepare one node to deploy a cluster, but this does not conform to the K8S design concept, so we recommend that you prepare at least 3 nodes:
 
 - **Two** nodes for starting the Seafile frontend service
 - **One** node for starting the Seafile backend service
@@ -235,13 +235,6 @@ When deploying a Seafile cluster using K8S, you can enable HTTPS and use load ba
 - External load balancing server, such as *Nginx*. Typically you will need to reverse proxy `http://<your control plane>/`
 - K8S Gateway API, e.g., [Nginx-gateway](https://docs.nginx.com/nginx-gateway-fabric/installation/installing-ngf/manifests/) and [Istio-gateway](https://istio.io/latest/docs/tasks/traffic-management/ingress/gateway-api/)
 
-Finally, you should modify the related URLs in `seahub_settings.py`, from `http://` to `https://`:
-
-```py
-SERVICE_URL = "https://seafile.example.com"
-FILE_SERVER_ROOT = 'https://seafile.example.com/seafhttp'
-```
-
 ## Log routing and aggregation system
 
 Similar to [Single-pod Seafile](./k8s_single_node.md), you can browse the log files of Seafile running directly in the persistent volume directory. The difference is that when using K8S to deploy a Seafile cluster (especially in a cloud environment), the persistent volume created is usually shared and synchronized for all nodes. However, ***the logs generated by the Seafile service do not record the specific node information where these logs are located***, so browsing the files in the above folder may make it difficult to identify which node these logs are generated from. Therefore, one solution proposed here is:
diff --git a/manual/setup_binary/https_with_nginx.md b/manual/setup_binary/https_with_nginx.md
index 530e14e4..88599849 100644
--- a/manual/setup_binary/https_with_nginx.md
+++ b/manual/setup_binary/https_with_nginx.md
@@ -226,24 +226,6 @@ Modify the following field to `https`
 SEAFILE_SERVER_PROTOCOL=https
 ```
 
-### Modifying seahub_settings.py
-
-!!! tip "More convenient"
-    The `SERVICE_URL` and `FILE_SERVER_ROOT` can also be modified in Seahub via **System Admininstration** > **Settings**.  If they are configured via System Admin and in seahub_settings.py, the value in System Admin will take precedence.
-
-- The `SERVICE_URL` in [seahub_settings.py](../config/seahub_settings_py.md) informs Seafile about the chosen domain, protocol and port. Change the `SERVICE_URL`so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the `http://` must not be removed):
-
-
-    ```python
-    SERVICE_URL = 'https://seafile.example.com'
-    ```
-
-- The `FILE_SERVER_ROOT` in [seahub_settings.py](../config/seahub_settings_py.md) informs Seafile about the location of and the protocol used by the file server. Change the `FILE_SERVER_ROOT` so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the trailing `/seafhttp` must not be removed):
-
-    ```python
-    FILE_SERVER_ROOT = 'https://seafile.example.com/seafhttp'
-    ```
-
 ### Modifying seafile.conf (optional)
 
 To improve security, the file server should only be accessible via Nginx.