More suggestions from review

Author: cwickham

docs/get-started/computations/positron.qmd

@@ -105,9 +105,9 @@ In addition to running a single code cell, there are a variety of other commands
 
 ## Tracking down code problems
 
-A good approach to trouble-shooting the code in your document
+A good approach to troubleshooting the code in your document
 is to restart your Console ({{< kbd mac=Cmd-Shift-0 win=Ctrl+Shift+0 linux=Ctrl+Shift+0 >}}), and **Quarto: Run All Cells** ({{< kbd mac=Cmd-Option-R win=Ctrl+Alt+R linux=Ctrl+Alt+R >}}). 
-This emulates Quarto's approach to executing the code in your document: starting a clean session, and executing code cells from top to bottom. 
+This emulates Quarto's approach to executing the code in your document: starting a clean session and executing code cells from top to bottom. 
 
 :::
 
@@ -154,7 +154,6 @@ Try this with the cell labelled `scatterplot`.
 ``` r
 #| label: scatterplot
 #| echo: true
-
 ggplot(mpg, aes(x = hwy, y = cty, color = cyl)) +
   geom_point(alpha = 0.5, size = 2) +
   scale_color_viridis_c() +
@@ -295,11 +294,11 @@ You can read more about how Quarto chooses an engine in [Engine Binding](/docs/c
 
 ## R 
 
-If you completed this tutorial with R, you'll have been using the `knitr` engine. 
+If you've been working through this tutorial with R, you have been using the `knitr` engine. 
 See [Knitr Cell Options](/docs/reference/cells/cells-knitr.qmd) documentation for the complete list of available code cell options.
 
 ## Python
-If you completed this tutorial with Python, you'll have been using the `jupyter` engine.
+If you've been working through this tutorial with Python, you have been using the `jupyter` engine.
 See the [Jupyter Cell Options](/docs/reference/cells/cells-jupyter.qmd) documentation for the complete list of available code cell options.
 
 :::
@@ -486,7 +485,7 @@ An alternative is to use inline code, which you'll cover next.
 
 Code cells using the `` ```{language} `` syntax are sometimes called *executable* code cells because they will be executed by the computational engine (e.g. `knitr` or `jupyter`).
 
-If you want to show code without it being processed by the computational engine use a code block:
+If you want to show code without it being processed by the computational engine, use a code block:
 
 ::: {.panel-tabset group="language"}
 
@@ -508,7 +507,7 @@ If you want to show code without it being processed by the computational engine
 
 :::
 
-You can read more, and see some syntax alternatives, at [Markdown Basics: Source Code](/docs/authoring/markdown-basics.qmd#source-code)
+You can read more and see some syntax alternatives at [Markdown Basics: Source Code](/docs/authoring/markdown-basics.qmd#source-code).
 
 :::
 
@@ -518,7 +517,7 @@ You can read more, and see some syntax alternatives, at [Markdown Basics: Source
 
 ## R
 
-To include executable expressions within markdown text, enclose the expression in `` `{r} ` ``^[Quarto also supports the Knitr syntax `` `r ` ``, read more in [Inline Code](/docs/computations/inline-code.qmd)].
+To include executable expressions within markdown text, enclose the expression in `` `{r} ` ``^[Quarto also supports the Knitr syntax `` `r ` ``, read more in [Inline Code](/docs/computations/inline-code.qmd).].  
 
 ## Python
 
@@ -557,7 +556,7 @@ You could now delete the code cell that did the same computation, since the inli
 If the expression you want to inline is more complex, involving many functions or a pipeline, we recommend including it in a code cell (with `echo: false`) and assigning the result to an object.
 Then, you can call that object in your inline code.
 
-For additional details on inline code expressions, visit the [Inline Code](/docs/computations/inline-code.qmd) page.
+For additional details on inline code expressions, visit the [Inline Code](/docs/computations/inline-code.qmd) documentation.  
 
 
 ## Final Document