Update BoringSSL to commit afe57cb14d36f70ad4a109fc5e7765d1adc67035

third_party/boringssl/README

Index: third_party/boringssl/README
diff --git a/third_party/boringssl/README b/third_party/boringssl/README
index f151cb27c8d69cad7240f9d2ab271f6630a203c9..e9e578aaf3aad7eb6d0f1a85312c018341cef9f9 100644
--- a/third_party/boringssl/README
+++ b/third_party/boringssl/README
@@ -5,13 +5,15 @@ src/util/generate_build_files.py chromium.
 
 That script is maintained by the chromium team, to make a gyp build
 of boringssl that does not require go or perl.  We modify the main
-gyp file of this build, boringssl.gyp, to add configurations for
+gyp file of chromium's build of boringssl,
+chromium/src/third_party/boringssl/boringssl.gyp, to add configurations for
 the target architectures, creating boringssl_dart.gyp.
 
-When updating boringssl in Dart, delete this directory,
-and check out the new boringssl to src.  Then run the script, check out
-our two files boringssl_dart.gyp and boringssl_configurations.gypi and commit
-the changes and any added or deleted files, as well as a change to the
-boringssl revision in DEPS.  If there are changes in boringssl.gyp,
-consider making  similar changes to boringssl_dart.gyp
-Test the changes on all platforms before committing, of course.
+When updating boringssl in Dart, delete this directory, and check out
+the new boringssl to src.  Then run the script and check out our files
+README, boringssl_dart.gyp, and boringssl_configurations.gypi.
+Finally, commit the changes and any added or deleted files, as well as
+a change to the boringssl revision in DEPS.  If there are changes in
+chromium's chromium/src/third_party/boringssl/boringssl.gyp, consider
+making similar changes to boringssl_dart.gyp Test the changes on all
+platforms before committing, of course.