Remove internal links from build instructions.
Signed-off-by: Dave Smith <smithdave@google.com>
Change-Id: I4bae139be9070f8d31a959787f4844f63928e4ec
diff --git a/GettingStarted.md b/GettingStarted.md
index 7d5a8d3..a24433f 100644
--- a/GettingStarted.md
+++ b/GettingStarted.md
@@ -28,21 +28,22 @@
```
Once you've done this, you're actually ready to check out the sources. Make a
-new directory where you'd like it to live. Depending on which board you will be
-building for determines which manifest you need in your init. Each XML file is
-named after the board's codename.
-
-Our default board type is the Coral Dev Board, also known by the codename
-`enterprise`, which is chosen by specifying the `enterprise.xml` manifest file.
+new directory where you'd like it to live, and initialize `repo` with the
+current release branch.
```
-repo init -u sso://aiyprojects/manifest -m enterprise.xml
+repo init -u https://coral.googlesource.com/manifest -b release-chef
repo sync -j$(nproc)
```
+The board you target determines which manifest you need to init. Each XML file is
+named after the board's codename. Our default board type is the Coral Dev Board,
+also known by the codename `enterprise` (defined in `enterprise.xml`).
+
A current list of boards that are supported is available in the [manifest
-project](https://aiyprojects.googlesource.com/manifest/+/refs/heads/master),
-listed by codename.
+project](https://coral.googlesource.com/manifest/+/refs/heads/master),
+listed by codename. To target a non-default manifest, add the `-m` flag to
+`repo init` with the name of the manifest XML file.
Note that some boards require specific groups to be enabled to pull down the
correct packages. Contact the authors for more information on what groups are
@@ -67,9 +68,6 @@
machine by following [Docker's official installation instructions for Docker
CE](https://docs.docker.com/install/).
-Googlers have specific security requirements on internal workstations and must
-follow the [install instructions here](http://go/installdocker).
-
### Fastboot
Mendel boards typically use the `fastboot` protocol for flashing boards, much
@@ -117,7 +115,7 @@
At this point you'll have a couple of extra functions available to navigate
around the tree and build things in part or in whole. See below for more
information, or simply [read the source
-here](https://aiyprojects.googlesource.com/build/+/refs/heads/master/setup.sh).
+here](https://coral.googlesource.com/build/+/refs/heads/master/setup.sh).
Now you can build the tree by running:
