Skip to content

Commit 1dab410

Browse files
Updated README.md (#179)
1 parent e61490e commit 1dab410

1 file changed

Lines changed: 3 additions & 4 deletions

File tree

README.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ Therefore, this part of portfolio is not customizable. But don't worry we have a
143143
144144
# Choose Theme 🌈
145145
146-
- You can take a look at `src/theme.js` file where all available themes are mentioned with respective color codes.
146+
- You can take a look at `src/theme.js` file where all available themes are mentioned with their respective color codes.
147147
- At the bottom of this file you will see the below code:
148148
- `export const chosenTheme = blueTheme;`
149149
- You need to change the name from `blueTheme` to whatever theme you want to set your website to.
@@ -162,9 +162,8 @@ Therefore, this part of portfolio is not customizable. But don't worry we have a
162162
**Option 1:**
163163
164164
- Run `npm run build` to generate the production build folder.
165-
- Enter the build folder, `git init` and push the generated code to the `master` branch of your new repository. That's it. Done.
166-
You may need to `git init` and force push at every new build.
167-
165+
- Enter the build folder, `git init` and push the generated code to the `master` branch of your new repository on github. That's it. It's Done.
166+
- You may need to `git init` and force push at every new build.
168167
**Option 2 (will not work with [user pages](https://docs.github.com/en/github/working-with-github-pages/about-github-pages)):**
169168
170169
- Run `npm run deploy` to build and create a branch called `gh-pages`. It will push the `build` files to that branch.

0 commit comments

Comments
 (0)