fix: update contributing docs

Author: wuweiweiwu

CONTRIBUTING.md

@@ -11,10 +11,11 @@ In return, they should reciprocate that respect in addressing your issue or asse
 
 The issue tracker is the preferred channel for bug reports but please respect the following restrictions:
 
-* Please **do not** use the issue tracker for personal support requests.
-* Please **do not** derail or troll issues. Keep the discussion on topic and respect the opinions of others.
+- Please **do not** use the issue tracker for personal support requests.
+- Please **do not** derail or troll issues. Keep the discussion on topic and respect the opinions of others.
 
 <a name="bugs"></a>
+
 ## Bug reports
 
 A bug is a _demonstrable problem_ that is caused by the code in the repository.
@@ -50,17 +51,17 @@ Example:
 > This might include the lines of code that you have identified as causing the bug,
 > and potential solutions (and your opinions on their merits).
 
-
 <a name="features"></a>
+
 ## Feature requests
 
 Feature requests are welcome.
 But take a moment to find out whether your idea fits with the scope and aims of the project.
-It's up to *you* to make a strong case to convince the project's developers of the merits of this feature.
+It's up to _you_ to make a strong case to convince the project's developers of the merits of this feature.
 Please provide as much detail and context as possible.
 
-
 <a name="pull-requests"></a>
+
 ## Pull requests
 
 Good pull requests - patches, improvements, new features - are a fantastic help.
@@ -123,23 +124,26 @@ Follow this process if you'd like your work considered for inclusion in the proj
    ```
 
 8. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
-    with a clear title and description.
+   with a clear title and description.
 
 **IMPORTANT**: By submitting a patch, you agree to allow the project owner to license your work under the same license as that used by this project (MIT).
 
 <a name="running-local-demo"></a>
+
 ## Running Local Demo
 
 You can run the local demo with yarn like so:
 
 ```bash
 cd <root>
-yarn start
+yarn build
+yarn website:start
 ```
 
 The local app will then be available at http://localhost:3000
 
 <a name="running-tests"></a>
+
 ## Running Tests
 
 All unit tests must pass before a pull request will be approved.

website/README.md

@@ -1,25 +1,16 @@
-This directory contains the source for [react-split-pane.surge.sh](https://react-split-pane.now.sh).
+This directory contains the source for [react-split-pane.surge.sh](https://react-split-pane.surge.sh).
 The website structure was created with [`create-react-app`](https://github.com/facebook/create-react-app), although it has since been ejected in order to add custom Webpack loaders.
 
 ## Local development
 
-To run this site locally, first make sure you have NPM linked `react-split-pane`:
-
-```sh
-cd /local/path/to/react-split-pane
-npm link
-cd ./website
-npm link react-split-pane
-```
-
-Then run the NPM "start" command in the project root to watch for changes to `react-split-pane`:
+Run the NPM "build:watch" command in the project root to watch for changes to `react-split-pane` and rebuild:
 
 ```sh
  cd /local/path/to/react-split-pane
- npm run start
+ npm run build:watch
 ```
 
-Lastly, run the NPM "start" command from this directory to run the local webserver:
+Lastly, run the NPM "start" command from the website directory to run the local webserver:
 
 ```sh
 cd /local/path/to/react-split-pane/website
@@ -28,7 +19,7 @@ npm run start
 
 ## Deployment
 
-To deploy this website to Now, use the NPM "deploy" command from this directory:
+To deploy this website to Surge, use the NPM "deploy" command from this directory:
 
 ```sh
 cd /local/path/to/react-split-pane/website