docs: added + updated build and deployment guides (#10019)

www/apps/book/app/learn/deployment/page.mdx

@@ -1,5 +1,5 @@
 export const metadata = {
-  title: `${pageNumber} Deployment Overview`,
+  title: `${pageNumber} Medusa Deployment Overview`,
 }
 
 # {metadata.title}
@@ -12,7 +12,7 @@ A standard Medusa project is made up of:
 
 - Medusa application: The Medusa server and the Medusa Admin.
 - One or more storefronts
-    
+
 ![Diagram showcasing the connection between the three deployed components](https://res.cloudinary.com/dza7lstvk/image/upload/v1708600807/Medusa%20Book/deployment-options_ceuuvo.jpg)
 
 You can either deploy the Medusa application fully (server with the admin), or deploy the Medusa Admin separately. The storefront is always deployed separately.
@@ -35,7 +35,11 @@ For optimal experience, make sure that the hosting provider and plan offer at le
 
 Your server connects to a PostgreSQL database, Redis, and other services relevant for your setup. Most hosting providers support deploying and managing these databases along with your Medusa server (such as Railway and DigitalOcean).
 
-Refer to [this reference](!resources!/deployment) to find how-to deployment guides for specific hosting providers.
+### How to Deploy Medusa?
+
+The [next chapter](./general/page.mdx) explains the general steps to deploy your Medusa application.
+
+Refer to [this reference](!resources!/deployment) to find how-to deployment guides for general and specific hosting providers.
 
 ---
 
@@ -51,7 +55,7 @@ In this scenario, make sure the hosting provider and plan of your choice provide
 
 <Note title="Tip">
 
-The server deployment guides mention details on how to deploy the admin with the Medusa server.
+The [server deployment guides](!resources!/deployment) mention details on how to deploy the admin with the Medusa server.
 
 </Note>