doc: rewrite run-on sentence in garbage collection discussion

Change-Id: I60cb7010448757ca4c7a2973bee2277b3d5fc439
Reviewed-on: https://go-review.googlesource.com/124175
Reviewed-by: Ian Lance Taylor <iant@golang.org>

diff --git a/doc/go_faq.html b/doc/go_faq.html
index 23df178febea110583927e3e0bcc2d75980a1694..13dc43284e950db72fe504e150e95447b44eb356 100644 (file)
--- a/doc/go_faq.html
+++ b/doc/go_faq.html
@@ -2348,9 +2348,9 @@ simpler because they don't need to specify how memory is managed across them.
 </p>
 
 <p>
-The current implementation is a mark-and-sweep collector that runs
-in parallel with the main program on a separate CPU core if the
-machine is a multiprocessor.
+The current implementation is a mark-and-sweep collector.
+If the machine is a multiprocessor, it runs on a separate CPU
+core in parallel with the main program.
 Major work on the collector in recent years has reduced pause times
 often to the sub-millisecond range, even for large heaps,
 all but eliminating one of the major objections to garbage collection