Update notification server related documents

manual/extension/notification-server.md

@@ -6,7 +6,6 @@ When a directory is opened on the web interface, the lock status of the file can
 
 The notification server uses websocket protocol and maintains a two-way communication connection with the client or the web interface. When the above changes occur, seaf-server will notify the notification server of the changes. Then the notification server can notify the client or the web interface in real time. This not only improves the real-time performance, but also reduces the performance overhead of the server.
 
-!!! danger "The notification server cannot work if you config Seafile server with SQLite database"
 
 ## Supported update reminder types
 
@@ -16,7 +15,7 @@ The notification server uses websocket protocol and maintains a two-way communic
 
 ## How to configure and run
 
-Since seafile-12.0.0, we use docker to deploy the notification server. First deploy Seafile docker, then download `notification-server.yml` and modify the `.env` file:
+Since Seafile 12.0, we use docker to deploy the notification server. First deploy Seafile docker, then download `notification-server.yml` and modify the `.env` file:
 
 ```sh
 wget https://manual.seafile.com/12.0/docker/notification-server.yml

manual/extension/only_office.md

@@ -1,6 +1,6 @@
 # OnlyOffice
 
-From version 6.1.0+ on (including CE), Seafile supports [OnlyOffice](https://www.onlyoffice.com/) to view/edit office files online. In order to use OnlyOffice, you must first deploy an OnlyOffice server. 
+Seafile supports [OnlyOffice](https://www.onlyoffice.com/) to view/edit office files online. In order to use OnlyOffice, you must first deploy an OnlyOffice server. 
 
 !!! tip "Deployment Tips"
 

manual/upgrade/upgrade_notes_for_12.0.x.md

@@ -18,6 +18,7 @@ Seafile version 12.0 has following major changes:
 * A new wiki module (still in beta, disabled by default)
 * A new trash mechanism, that deleted files will be recorded in database for fast listing. In the old version, deleted files are scanned from library history, which is slow.
 * Community edition now also support online GC (because SQLite support is dropped)
+* Notification server is now packaged into its own docker image.
 
 Other changes:
 
@@ -80,18 +81,25 @@ Note: JWT_PRIVATE_KEY, A random string with a length of no less than 32 characte
 
 ### 4) Start Seafile-12.0.x server
 
-### Upgrade notification server
+### 5) Upgrade notification server
 
-Since seafile-12.0.0, we use docker to deploy the notification server. Please follow the document to [enable notification server](../extension/notification-server.md)
+Since seafile-12.0.0, we use docker to deploy the notification server. Please follow the document of [notification server](../extension/notification-server.md).
+
+!!! note [Notification server and Seafile binary package]
+    Deploying notification server and **Seafile binary package** on the same server is no longer officially supported. You will need to add Nginx rules for notification server properly.
+
+The recommendation is to
 
 ## Upgrade SeaDoc from 0.8 to 1.0
 
 If you have deployed SeaDoc v0.8 with Seafile v11.0, you can upgrade it to 1.0 use the following two steps:
 
 1. Delete sdoc_db.
-2. Re-deploy SeaDoc server. In other words, delete the old SeaDoc deployment and deploy a new SeaDoc server on a separate machine.
+2. Re-deploy SeaDoc server. In other words, delete the old SeaDoc deployment and re-deploy a new SeaDoc server.
+
+!!! note [SeaDoc and **Seafile binary package**]
+    Deploying SeaDoc and **Seafile binary package** on the same server is no longer officially supported. You will need to add Nginx rules for SeaDoc server properly.
 
-Note, deploying SeaDoc and **Seafile binary package** on the same server is no longer supported. If you really want to deploying SeaDoc and Seafile server on the same machine, you should deploy Seafile server with Docker.
 
 ### Delete sdoc_db