✒ Spell Check All .md Files Related to Flutter 💙 (#61564)

* 🐛 Fix Spelling Issues in Main README.md

* 🐛 Fix spelling issues in dev README.md

* 🐛 Fix spelling issues in complex_layout README.md

* 🐛 Fix spelling issues in macrobenchmarks README.md

* 🐛 Fix spelling issues in platform_views_layout README.md

* 🐛 Fix spelling issues in test_Apps/stocks README.md

* 🐛 Fix spelling issues in bots README.md

* ✒ Spell Check dev/ci README.md

* ✒ Spell Check dev/ci/docker_linux README.md

* ✒ Spell Check dev/devicelab README.md

* ✒ Spell Check dev/docs README.md

* ✒ Spell Check dev/snippets README.md

* ✒ Spell Check dev/snippets/config/templates README.md

* ✒ Spell Check dev/tools/gen_keycodes README.md

* ✒ Spell Check dev/tools/vitool README.md

* ✒ Spell Check examples/catalog README.md

* ✒ Spell Check examples/flutter_view README.md

* ✒ Spell Check examples/image_list README.md

* ✒ Spell Check examples/layers README.md

* ✒ Spell Check examples/platform_channel README.md

* ✒ Spell Check examples/platform_channel_swift README.md

* ✒ Spell Check examples/platform_view README.md

* ✒ Spell Check packages/_flutter_web_build_script README.md

* ✒ Spell Check packages/flutter_localizations README.md

* ✒ Spell Check packages/flutter_tools README.md

* ✒ Spell Check CODE_OF_CONDUCT.md

* ✒ Spell Check dev/integration_test/android_splash_screens/splash_Screen_load_rotate README.md

* ✒ Spell Check dev/integration_test/android_views README.md

* ✒ Spell Check dev/integration_tests/flutter_driver_screenshot_test README.md

* ✒ Spell Check dev/integration_tests/flutter_gallery README.md

* ✒ Spell Check dev/integration_tests/gradle_deprecated_settings README.md

* ✒ Spell Check dev/integration_tests/ios_add2app_life_cycle README.md

* ✒ Spell Check dev/integration_tests/ios_host_app README.md

* ✒ Spell Check dev/integration_tests/ios_platform_view_tests README.md

* ✒ Spell Check dev/automated_tests/flutter_test README.md

* ✒ Spell Check .github/PULL_REQUEST_TEMPLATE.md

* ✒ Spell Check .hithub/ISSUE_TEMPLATE/ACTIVATION.md

* ✒ Spell Check .github/ISSUE_TEMPLATE/BUG.md

* ✒ Spell Check .github/ISSUE_TEMPLATE/feature_request.md

* ✒ Spell Check .github/ISSUE_TEMPLATE/performance_others.md

* ✒ Spell Check .github/ISSUE_TEMPLATE/performance_speed.md

* ✒ Spell Check packages/flutter_tools/doc/daemon.md

* ✒ Spell Check packages/flutter_tools/fuchsia_enrtypoint_shim/README.md

* ✒ Minimize line to 80 columns

* ✒ Minimize line to 80 columns

* ✒ Fix Typo

* ✒ Chnaged numbers to 1 for testing purposes

* ✒ Changed numbers to 1 for testing purposes

* ❌ Remove 'a' which is a typo

* ✒ Change a sentence to be better

* ✒ Remove 'a' which is a typo

* ✒ Fix small issue

* ✒ Fix small typo

* ✒ Fix some typos

* ❌ Remove trailing space

* ❌ Remove trailing space

* 🐛 Fix small typo

* ✒ Fix Typo

* 🐛 Fix small bug

dev/snippets/README.md

@@ -22,15 +22,15 @@ There are three kinds of code blocks.
   magically determine how to analyze, and
 
 * A `dartpad` sample, which gets placed into a full-fledged application, and can
-  be actually executed inline in the documentation on the web page using
+  be executed inline in the documentation on the web page using
   DartPad.
 
 * A `sample`, which gets placed into a full-fledged application, but isn't
   placed into DartPad in the documentation because it doesn't make sense to do
   so.
 
-Ideally every sample is a DartPad sample, but some samples don't have any visual
-representation, and some just don't make sense that way (for example, sample
+Ideally, every sample is a DartPad sample, but some samples don't have any visual
+representation and some just don't make sense that way (for example, sample
 code for setting the system UI's notification area color on Android won't do
 anything on the web).
 
@@ -70,7 +70,7 @@ There are several kinds of sample code you can specify:
 
 * Constructor calls, typically showing what might exist in a build method. These
   will be inserted into an assignment expression assigning to a variable of type
-  "dynamic" and followed by a semicolon, for the purposes of analysis.
+  "dynamic" and followed by a semicolon, for analysis.
 
 * Class definitions. These start with "class", and are analyzed verbatim.
 
@@ -79,7 +79,7 @@ There are several kinds of sample code you can specify:
   individually.
 
 The above means that it's tricky to include verbatim imperative code (e.g. a
-call to a method), since it won't be valid to have such code at the top level.
+call to a method) since it won't be valid to have such code at the top level.
 Instead, wrap it in a function or even a whole class, or make it a valid
 variable declaration.
 
@@ -151,7 +151,7 @@ This command is displayed as part of the sample in the API docs.
 
 #### Templates
 
-In order to support showing an entire app when you click on the right tab of the
+To support showing an entire app when you click on the right tab of the
 code sample UI, we have to be able to insert the `sample` or `dartpad` block
 into the template and instantiate the right parts.
 
@@ -171,7 +171,7 @@ specified template.
 
 ## Skeletons
 
-A skeleton (in relation to this tool) is an HTML template into which the Dart
+A skeleton (concerning this tool) is an HTML template into which the Dart
 code blocks and descriptions are interpolated.
 
 There is currently one skeleton for
@@ -180,11 +180,11 @@ There is currently one skeleton for
 [snippet](config/skeletons/snippet.html) code samples, but there could be more.
 
 Skeletons use mustache notation (e.g. `{{code}}`) to mark where components will
-be interpolated into the template. It doesn't actually use the mustache
-package, since these are simple string substitutions, but it uses the same
+be interpolated into the template. It doesn't use the mustache
+package since these are simple string substitutions, but it uses the same
 syntax.
 
-The code block generation tools process the source input and emit HTML for
+The code block generation tools that process the source input and emit HTML for
 output, which dartdoc places back into the documentation. Any options given to
 the `{@tool ...}` directive are passed on verbatim to the tool.