Update README.md

[mafaulkner]

General: Labs are done by individuals, not "us." I don't know what the tag "walkthrough-editor-spotlight" means. Can you just tag as code? Lines 12 - 16: Use bullets instead of numbers. The steps in the procedures, however, should be numbered. Line 12: Specify what "this app" is. Line 15: Is "the application" the same as "this app"? It's not clear. Line 24: Use numbers for procedure steps. Line 24: First tell the learner where to run this command. Is it in Cloud Shell? If so, tell the learner how to open Cloud Shell. See an example in go/lab-guide-guidelines. Line 42: Deleted this line because it interrupts the flow of the procedure and doesn't offer new information. Line 50: This is not a user action so shouldn't be a step. Instead, indent it under the previous step as a result. Line 59: Does the learner do anything with this code, or is just showing where the Web Preview link is? If the latter, you can delete it (and adjust the previous line). Line 65: I deleted the "Next" sentence because the same information is in the next procedure. Line 85: This is not a user action so shouldn't be a step. Instead, indent it under the previous step as a result. That means that the procedure has only one step, so use a bullet for it instead of a number. Line 112: If the app returns "Hello world," why was "Hello Anthos" the expected result in line 101? Also, should "world" be capped or lowercase? These two instances are inconsistent. Line 123: This is not a user action so shouldn't be a step. Instead, indent it under the previous step as a result. Line 151: This is not a user action so shouldn't be a step. Instead, indent it under the previous step as a result. Line 159: This is not a user action either. Format it as a note. Line 194: What is the name of this button? Use this language: Click button name (icon image)...

[google-cla[bot]]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.