From fb02750d9aea47fc526a826c41323155fb3a9f8b Mon Sep 17 00:00:00 2001 From: Yangshun Tay Date: Sat, 7 Oct 2017 01:19:55 +0800 Subject: [PATCH] Fix repo URLs --- README.md | 8 ++++---- content/docs/codebase-overview.md | 2 +- src/components/MarkdownPage/MarkdownPage.js | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 5a134c65..0f55125c 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ This repo contains the source code and documentation powering [reactjs.org](http 1. Git 1. Node: install version 8.4 or greater 1. Yarn: `npm i -g yarn` to install it globally via NPM -1. A clone of the [reactjs.org repo](https://github.com/facebook/reactjs.org) on your local machine +1. A clone of the [reactjs.org repo](https://github.com/reactjs/reactjs.org) on your local machine 1. A fork of the repo (for any contributions) ### Installation @@ -26,7 +26,7 @@ This repo contains the source code and documentation powering [reactjs.org](http ### Create a branch -1. `git checkout master` from any folder in your local react repository +1. `git checkout master` from any folder in your local `reactjs.org` repository 1. `git pull origin master` to ensure you have the latest main code 1. `git checkout -b the-name-of-my-branch` (replacing `the-name-of-my-branch` with a suitable name) to create a branch @@ -47,10 +47,10 @@ This repo contains the source code and documentation powering [reactjs.org](http 1. `git add -A && git commit -m "My message"` (replacing `My message` with a commit message, such as `Fixed header logo on Android`) to stage and commit your changes 1. `git push my-fork-name the-name-of-my-branch` -1. Go to the [reactjs.org repo](https://github.com/facebook/reactjs.org) and you should see recently pushed branches. +1. Go to the [reactjs.org repo](https://github.com/reactjs/reactjs.org) and you should see recently pushed branches. 1. Follow GitHub's instructions. 1. If possible include screenshots of visual changes. A Netlify build will also be automatically created once you make your PR so other people can see your change. ## Troubleshooting -- `yarn reset` to clear the local cache \ No newline at end of file +- `yarn reset` to clear the local cache diff --git a/content/docs/codebase-overview.md b/content/docs/codebase-overview.md index f87b9418..6a9ec2b5 100644 --- a/content/docs/codebase-overview.md +++ b/content/docs/codebase-overview.md @@ -66,7 +66,7 @@ The [fbjs repository](https://github.com/facebook/fbjs) exists because React sha After cloning the [React repository](https://github.com/facebook/react), you will see a few top-level folders in it: * [`src`](https://github.com/facebook/react/tree/master/src) is the source code of React. **If your change is related to the code, `src` is where you'll spend most of your time.** -* [`docs`](https://github.com/facebook/react/tree/master/docs) is the React documentation website. When you change APIs, make sure to update the relevant Markdown files. +* [`docs`](https://github.com/reactjs/reactjs.org/tree/master/content) is the React documentation website. When you change APIs, make sure to update the relevant Markdown files. * [`fixtures`](https://github.com/facebook/react/tree/master/fixtures) contains a few small React test applications for contributors. * [`packages`](https://github.com/facebook/react/tree/master/packages) contains metadata (such as `package.json`) for all packages in the React repository. Nevertheless, their source code is still located inside [`src`](https://github.com/facebook/react/tree/master/src). * `build` is the build output of React. It is not in the repository but it will appear in your React clone after you [build it](/docs/how-to-contribute.html#development-workflow) for the first time. diff --git a/src/components/MarkdownPage/MarkdownPage.js b/src/components/MarkdownPage/MarkdownPage.js index d4864461..d7f66b90 100644 --- a/src/components/MarkdownPage/MarkdownPage.js +++ b/src/components/MarkdownPage/MarkdownPage.js @@ -87,7 +87,7 @@ const MarkdownPage = ({
Edit this page