From e526ce3c47e2884a0ab9d6e3dfc7e91be12d2990 Mon Sep 17 00:00:00 2001 From: JonHolman Date: Tue, 15 Oct 2019 20:48:16 -0400 Subject: [PATCH] Fix minor typo frotend to frontend --- _chapters/automating-react-deployments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_chapters/automating-react-deployments.md b/_chapters/automating-react-deployments.md index 95576204e..7aa159234 100644 --- a/_chapters/automating-react-deployments.md +++ b/_chapters/automating-react-deployments.md @@ -8,7 +8,7 @@ ref: automating-react-deployments comments_id: automating-react-deployments/188 --- -Now that we have our backend deployed to production, we are ready to deploy our frotend to production as well! We'll be using a service called [Netlify](https://www.netlify.com) to do this. Netlify will not only host our React app, it'll also help automate our deployments. It's a little like what we did for our serverless API backend. We'll configure it so that it'll deploy our React app when we push our changes to Git. However, there are a couple of subtle differences between the way we configure our backend and frontend deployments. +Now that we have our backend deployed to production, we are ready to deploy our frontend to production as well! We'll be using a service called [Netlify](https://www.netlify.com) to do this. Netlify will not only host our React app, it'll also help automate our deployments. It's a little like what we did for our serverless API backend. We'll configure it so that it'll deploy our React app when we push our changes to Git. However, there are a couple of subtle differences between the way we configure our backend and frontend deployments. 1. Netlify hosts the React app on their infrastructure. In the case of our serverless API backend, it was hosted on our AWS account.