Corrected minor typos found in review.

Author: freakboy3742

Apple/__main__.py

@@ -225,7 +225,7 @@ def build_python_path() -> Path:
 
 @contextmanager
 def group(text: str):
-    """A context manager that ouptut a log marker around a section of a build.
+    """A context manager that output a log marker around a section of a build.
 
     If running in a GitHub Actions environment, the GitHub syntax for
     collapsible log sections is used.
@@ -438,7 +438,7 @@ def framework_path(host_triple: str, multiarch: str) -> Path:
 
 
 def package_version(prefix_path: Path) -> str:
-    """Extract the Python version being build from patchlevel.h."""
+    """Extract the Python version being built from patchlevel.h."""
     for path in prefix_path.glob("**/patchlevel.h"):
         text = path.read_text(encoding="utf-8")
         if match := re.search(
@@ -823,8 +823,8 @@ def parse_args() -> argparse.Namespace:
             "A tool for managing the build, package and test process of "
             "CPython on Apple platforms."
         ),
-        suggest_on_error=True,
     )
+    parser.suggest_on_error = True
     subcommands = parser.add_subparsers(dest="subcommand", required=True)
 
     clean = subcommands.add_parser(

Apple/iOS/README.md

@@ -56,7 +56,7 @@ The `Apple` subfolder of the Python repository acts as a build script that
 can be used to coordinate the compilation of a complete iOS XCframework. To use
 it, run::
 
-  python Apple iOS build
+  python Apple build iOS
 
 This will:
 
@@ -222,7 +222,7 @@ simulator build with a deployment target of 15.4.
 
 Once you have a built an XCframework, you can test that framework by running:
 
-  $ python Apple iOS test
+  $ python Apple test iOS
 
 ### Testing a single-architecture framework
 
@@ -258,7 +258,7 @@ project, and then boot and prepare the iOS simulator.
 
 ### Debugging test failures
 
-Running `python Apple iOS test` generates a standalone version of the
+Running `python Apple test iOS` generates a standalone version of the
 `Apple/testbed` project, and runs the full test suite. It does this using
 `Apple/testbed` itself - the folder is an executable module that can be used
 to create and run a clone of the testbed project. The standalone version of the

Mac/Resources/framework/Info.plist.in

@@ -24,8 +24,6 @@
 	<string>????</string>
 	<key>CFBundleVersion</key>
 	<string>%VERSION%</string>
-	<key>MinimumOSVersion</key>
-	<string>@MACOSX_DEPLOYMENT_TARGET@</string>
 	<key>CFBundleAllowMixedLocalizations</key>
 	<true/>
 </dict>