python · terryjreedy · May 28, 2021 · terryjreedy · May 28, 2021 · Ayushparikh-code
diff --git a/README.rst b/README.rst
-workload.  This is necessary in order to profile the interpreter execution.
-Note also that any output, both stdout and stderr, that may appear at this step
+workload.  This is necessary to profile the interpreter's execution.
+Note also that any output, both stdout, and stderr, that may appear at this step
diff --git a/README.rst b/README.rst
 is suppressed.

 The final step is to build the actual interpreter, using the information
-collected from the instrumented one.  The end result will be a Python binary
+collected from the instrumented one.  The result will be a Python binary
diff --git a/README.rst b/README.rst
diff --git a/Misc/NEWS.d/next/Documentation/2021-05-26-18-29-48.bpo-39798.D4UZnR.rst b/Misc/NEWS.d/next/Documentation/2021-05-26-18-29-48.bpo-39798.D4UZnR.rst
@@ -0,0 +1 @@
+updated and corrected readme with some grammatical mistakes
diff --git a/README.rst b/README.rst
+flags for each flavor. Note that this is just an intermediary step.  The
+binary resulting from this step is not good for real-life workloads as it has
diff --git a/README.rst b/README.rst
-workload.  This is necessary in order to profile the interpreter execution.
-Note also that any output, both stdout and stderr, that may appear at this step
+workload.  This is necessary to profile the interpreter's execution.
+Note also that any output, both stdout, and stderr, that may appear at this step
		@@ -0,0 +1 @@
		updated and corrected readme with some grammatical mistakes
		flags for each flavor. Note that this is just an intermediary step. The
		binary resulting from this step is not good for real-life workloads as it has