From 3143db5a8e33681609c11e688f2b3d86789ea001 Mon Sep 17 00:00:00 2001 From: Strek Date: Fri, 21 Jan 2022 23:59:31 +0530 Subject: [PATCH] Updates deployment in readme from netlify to vercel (#4225) * updates readme * removed hosting provider name --- README.md | 2 +- beta/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ce68bb7a7..0482eb8c9 100644 --- a/README.md +++ b/README.md @@ -53,7 +53,7 @@ The documentation is divided into several sections with a different tone and pur 1. `git push my-fork-name the-name-of-my-branch` 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](https://www.netlify.com/) build will also be automatically created once you make your PR so other people can see your change. +1. If possible, include screenshots of visual changes. A preview build is triggered after your changes are pushed to GitHub. ## Translation diff --git a/beta/README.md b/beta/README.md index 85f6703e9..725a2c382 100644 --- a/beta/README.md +++ b/beta/README.md @@ -56,7 +56,7 @@ The documentation is divided into several sections with a different tone and pur 1. `git push my-fork-name the-name-of-my-branch` 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](https://www.netlify.com/) build will also be automatically created once you make your PR so other people can see your change. +1. If possible, include screenshots of visual changes. A preview build is triggered after your changes are pushed to GitHub. ## Translation