Update documentation to note the Chromium commit SHA to generate patches

Also fix a typo in the patch I just rebased.

Author: boomanaiden154

docs/regalloc-demo/demo.md

@@ -89,6 +89,12 @@ git apply $WORKING_DIR/ml-compiler-opt/experimental/chromium-thinlto-corpus-extr
 This will make a `clang_embed_bitcode` flag and a `lld_emit_index` flag
 available in the gn configuration.
 
+**Note:** These patches may or may not work depending on code churn within the
+Chromium code base. They were generated with Chromium at commit
+`ee3114540941f915c673c85d1f21b9c16a42a287`. Doing a full fetch (i.e., omitting
+the `--no-history` flag) and then checking out that commit will give the best
+chance of success.
+
 Now that this is all in place, you need to run the Chromium hooks in order to
 get the development environment ready for a full compilation:
 

experimental/chromium-bitcode-embedding.patch

@@ -8,7 +8,7 @@ index 1aad3d60b8404..c600c0edf481c 100644
    clang_base_path = default_clang_base_path
 +
 +  # Specifies whether or not bitcode should be embedded in all compiled targets
-+  clang_embit_bitcode = false
++  clang_embed_bitcode = false
  }
 diff --git a/build/config/compiler/BUILD.gn b/build/config/compiler/BUILD.gn
 index e89b62eb0aaf6..58bcaac2ffbf8 100644