docs: correct flow homepage url (#814)

<!-- Please provide enough information so that others can review your pull request. --> <!-- Keep pull requests small and focused on a single change. --> ### Summary Flow links to TypeScript homepage. ### Test plan <!-- List the steps with which we can test this change. Provide screenshots if this changes anything visual. -->

Author: finalchild

docs/pages/build.md

@@ -227,7 +227,7 @@ This option has no effect when overriding the default babel configuration withou
 
 ##### `copyFlow`
 
-If your source code is written in [Flow](http://www.typescriptlang.org/), You can specify the `copyFlow` option to `true` to copy the source files as `.js.flow` to the output folder. If the `main` entry in `package.json` points to the `index` file in the output folder, the flow type checker will pick these files up to use for type definitions.
+If your source code is written in [Flow](https://flow.org/), You can specify the `copyFlow` option to `true` to copy the source files as `.js.flow` to the output folder. If the `main` entry in `package.json` points to the `index` file in the output folder, the flow type checker will pick these files up to use for type definitions.
 
 ##### `sourceMaps`
 
@@ -255,7 +255,7 @@ Example:
 
 #### `typescript`
 
-Enable generating type definitions with `tsc` if your source code is written in [TypeScript](http://www.typescriptlang.org/).
+Enable generating type definitions with `tsc` if your source code is written in [TypeScript](https://www.typescriptlang.org/).
 
 When both `module` and `commonjs` targets are enabled, and `esm` is set to `true` for the `module` target, this will output 2 sets of type definitions: one for the CommonJS build and one for the ES module build.