Headers updates (#1664)

* headers update

* update 1

* updates

* Update products/pages/src/content/migrations/migrating-from-netlify/index.md

Co-authored-by: Luke Edwards <[email protected]>

* Update products/pages/src/content/migrations/migrating-from-netlify/index.md

* Update products/pages/src/content/platform/known-issues.md

Co-authored-by: Luke Edwards <[email protected]>

Author: deadlypants1973

products/pages/src/content/migrations/migrating-from-netlify/index.md

@@ -6,40 +6,42 @@ pcx-content-type: tutorial
 
 # Migrating from Netlify to Pages
 
-In this tutorial, you'll learn how to deploy your Netlify application to Cloudflare Pages.
+In this tutorial, you will learn how to deploy your Netlify application to Cloudflare Pages.
 
 <Aside>
-You should already have an existing project deployed on Netlify that you'd like to host on Cloudflare Pages. Features such as Netlify's Forms and Serverless Functions are currently not supported in Cloudflare Pages.
+
+Features such as Netlify's Forms and Serverless Functions are currently not supported in Cloudflare Pages. Cloudflare Pages does not directly support HTTP header customization, but it can be done through Workers. Refer to the ["Add custom HTTP headers"](/how-to/add-custom-http-headers) guide for more information.
+
 </Aside>
 
 ## Finding your build command and build directory
 
-To move your application to Cloudflare Pages, you'll need to find your build command and build directory. Cloudflare Pages will use this information to build your application and deploy it.
+To move your application to Cloudflare Pages, find your build command and build directory. Cloudflare Pages will use this information to build and deploy your application.
 
 In your Netlify Dashboard, find the project that you want to deploy. It should be configured to deploy from a GitHub Repo.
 
 ![Selecting a site in the Netlify Dashboard](./netlify-deploy-1.png)
 
-Inside of your site dashboard, select "Site Settings", and then "Build & Deploy".
+Inside of your site dashboard, select **Site Settings**, and then **Build & Deploy**.
 
 ![Selecting Site Settings in site dashboard](./netlify-deploy-2.png)
 
 ![Selecting Build and Deploy in sidebar](./netlify-deploy-3.png)
 
-In the "Build & deploy" tab, find the "Build settings" panel, which will have the **Build command** and **Publish directory** fields. Save these for deploying to Cloudflare Pages! In the below image, my **Build command** is `yarn build`, and my **Publish directory** is `build/`.
+In the **Build & Deploy** tab, find the **Build settings** panel, which will have the **Build command** and **Publish directory** fields. Save these for deploying to Cloudflare Pages. In the below image, **Build command** is `yarn build`, and **Publish directory** is `build/`.
 
 ![Finding the "Build command" and "Publish directory" fields](./netlify-deploy-4.png)
 
 ## Creating a new Pages project
 
-Once you've found your build directory and build command, you can move your project to Cloudflare Pages.
+Once you have found your build directory and build command, you can move your project to Cloudflare Pages.
 
 The [Getting started guide](/getting-started) will show you how to add your GitHub project to Cloudflare Pages.
 
 If you choose to use a custom domain for your Pages, you can set it to the same custom domain as your currently deployed Netlify application. When Pages finishes the initial deploy of your site, you will need to delete the Workers application to start sending requests to Cloudflare Pages.
 
 ## Cleaning up your old application and assigning the domain
 
-In your DNS settings for your domain, make sure that you've updated the CNAME record for your domain from Netlify to Cloudflare Pages. With your DNS record updated, requests will go to your Pages application.
+In **DNS** on the Cloudflare dashboard, review that you have updated the CNAME record for your domain from Netlify to Cloudflare Pages. With your DNS record updated, requests will go to your Pages application.
 
-Congrats! You've migrated your Netlify project to Cloudflare Pages.
+With the above steps completed, you have successfully migrated your Netlify project to Cloudflare Pages.

products/pages/src/content/platform/known-issues.md

@@ -7,5 +7,6 @@ Here are some known bugs and issues that we're aware of with Cloudflare Pages:
 - pages.dev subdomains currently can't be changed. If you need to change your pages.dev subdomain, delete your project and create a new one.
 - Hugo builds automatically run an old version. To run the latest version of Hugo (for instance, 0.80.0), you'll need to set an environment variable. Set `HUGO_VERSION` to `0.80.0` or the Hugo version of your choice.
 - By default, we use Node 10 in the Pages build environment. If you need to use a newer Node version, see our [Build configuration page](https://developers.cloudflare.com/pages/platform/build-configuration) for configuration options.
+- For users migrating from Netifly, Cloudflare does not support Netlify's Forms and Serverless Functions features. Cloudflare Pages does not directly support HTTP header customization, but it can be done through Workers. Refer to the ["Add custom HTTP headers"](/how-to/add-custom-http-headers) guide for more information.
 
 Having an issue that you don't see listed above? Let us know in the Cloudflare Workers Discord. Get your invite at [discord.gg/cloudflaredev](https://discord.gg/cloudflaredev), and share your bug report in the #pages-help channel.