diff --git a/manual/extension/setup_seadoc.md b/manual/extension/setup_seadoc.md
index 9814c181..4ee58c42 100644
--- a/manual/extension/setup_seadoc.md
+++ b/manual/extension/setup_seadoc.md
@@ -25,7 +25,7 @@ The SeaDoc archticture is demonstrated as below:
 Here is the workflow when a user open sdoc file in browser
 
 1. When a user open a sdoc file in the browser, a file loading request will be sent to Caddy, and Caddy proxy the request to SeaDoc server (see [Seafile instance archticture](../setup/overview.md) for the details).
-2. SeaDoc server will send the file's content back if it is already cached, otherwise SeaDoc serve will sends a request to Seafile server.
+2. SeaDoc server will send the file's content back if it is already cached, otherwise SeaDoc server will sends a request to Seafile server.
 3. Seafile server loads the content, then sends it to SeaDoc server and write it to the cache at the same time.
 4. After SeaDoc receives the content, it will be sent to the browser.