diff --git a/docs/guides/deploy-warp-route.mdx b/docs/guides/deploy-warp-route.mdx
index 952bd161..9807bb44 100644
--- a/docs/guides/deploy-warp-route.mdx
+++ b/docs/guides/deploy-warp-route.mdx
@@ -24,7 +24,7 @@ To deploy the route, you will need a Warp Route config file. A valid config will
 * _Optional:_ Hyperlane connection details including contract addresses for the [mailbox](../reference/messaging/messaging-interface.mdx), [interchain gas](../reference/hooks/interchain-gas.mdx), and [interchain security modules](../reference/ISM/specify-your-ISM.mdx).
 * _Optional:_ The token standard - fungible tokens using ERC20 or NFTs using ERC721. Defaults to ERC20.
 
-The easiest way to create one is with the CLI's config comamnd:
+The easiest way to create one is with the CLI's config command:
 
 ```bash
 hyperlane config create warp
@@ -35,6 +35,11 @@ hyperlane config create warp
 If your config looks correct, you can now skip to [Step 2: Deployment](#2-deployment).
 Or see below for details on how to define your config manually.
 
+If you want to use custom chains(To use custom chains, first you need to [deploy Hyperlane](../deploy-hyperlane.mdx) onto your chain) in your Warp Route config, use the `--chains` flag. 
+```bash
+hyperlane config create warp --chains <PATH-TO-CHAINS-FILE>
+```
+
 :::
 
 #### Base
@@ -90,6 +95,15 @@ Run the following command to initiate the Warp Route deployment:
 hyperlane deploy warp
 ```
 
+:::tip
+
+If you are using custom chains(To use custom chains, first you need to [deploy Hyperlane](../deploy-hyperlane.mdx) onto your chain) in your Warp Route config, don't forget to use the `--chains` flag.
+```bash
+hyperlane deploy warp --chains <PATH-TO-CHAINS-FILE>
+```
+
+:::
+
 Once finished, the CLI will create two new JSON artifact files: `warp-deployment` and `warp-ui-token-config`. The first contains just addresses for the newly deployed Warp router contracts. The second is a config file for the Warp UI, which you can use for the next optional step.
 
 ## 3. Testing