From ecbef013a13357b595747abb5d67c25f7ea95d1e Mon Sep 17 00:00:00 2001
From: weru <onewesh@gmail.com>
Date: Tue, 06 Oct 2020 20:24:10 +0000
Subject: [PATCH] update

---
 README.md |   13 ++-----------
 1 files changed, 2 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index 96ad52f..caf1baf 100644
--- a/README.md
+++ b/README.md
@@ -34,16 +34,7 @@
 
 You can neutralize that drawback by forking the repo instead and following the same approach. Be sure the edit the `theme = ["github.com/onweru/compose"]` from the config.toml file appropriately.
 
-> :warn: If you choose __Option 2__ or __Option 3__ below, ensure you edit the following lines in the `config.toml` file ad advised on the comments
-
-```bash
-...
-# this example loads the theme as hugo module
-# comment out line below, and uncomment the line after it if you prefer to load the theme normally
-theme = ["github.com/onweru/compose"] # edit this if you'ld rather use a fork of this repo
-# theme = "compose"
-...
-```
+> ⚠️ If you choose __Option 2__ or __Option 3__ below, ensure you edit [these lines in the config.toml file](https://github.com/onweru/compose/blob/b3e30e0816621223224897edc45eeeabd0d9cd16/exampleSite/config.toml#L4-L7) as advised on the comments
 
 ### Option 2 (recommended)
 
@@ -75,7 +66,7 @@
 hugo server --themesDir ../..
 ```
 
-> Although, option 2 is great for quick testing, it is somewhat problematic when you want to update your theme. You would need to be careful not to overwrite your changes.
+> Although, option 3 is great for quick testing, it is somewhat problematic when you want to update your theme. You would need to be careful not to overwrite your changes.
 
 Once set, jump over to the `config.toml` file and start [configuring](#configuration) your site.
 

--
Gitblit v1.10.0