Apply suggestions from code review

Co-authored-by: Charlotte Wickham <[email protected]>

Author: MichaelHatherly

docs/computations/julia.qmd

@@ -12,11 +12,11 @@ Quarto supports executable Julia code blocks within markdown. This allows you to
 
 Quarto has two available engines for executing Julia code. The older one is using the [IJulia](https://github.com/JuliaLang/IJulia.jl) Jupyter kernel and depends on Python to run. The newer engine is using the [QuartoNotebookRunner.jl](https://github.com/PumasAI/QuartoNotebookRunner.jl/) package to render notebooks and does not have any additional dependencies beyond a Julia installation.
 
-To use either of these engines will require that you manually install Julia if
+Using either of these engines will require manually installing Julia if
 you have not done so already. You can download it from
 https://julialang.org/downloads/. There are two options for installation: the
-Juliaup installation manager, and the "manual" installation approach. Unless
-you know that you need to use the "manual" approach you should prefer using
+Juliaup installation manager, or the "manual" installation approach. Unless
+you know that you need to use the "manual" approach, use
 Juliaup since it allows you to manage multiple Julia versions on your system.
 
 ## Using the `jupyter` engine
@@ -371,7 +371,7 @@ provided to Julia, unlike the behaviour of a Julia REPL session.
 ### Caching {#caching-julia}
 
 The engine has built-in support for caching notebook results. This feature is disabled by
-default but can be enabled by setting `execute.cache` option to `true` in a notebook's
+default but can be enabled by setting the `execute.cache` option to `true` in a notebook's
 frontmatter:
 
 ````markdown
@@ -390,7 +390,7 @@ rand()
 Notebook caches are invalidated based on the following criteria:
 
 - Using a different Julia version to run the notebook.
-- The `Manifest.toml` of the environment the notebook is run in. Adding, removing, or changing package versions will invalidate the cache.
+- Changes to the `Manifest.toml` of the environment the notebook is run in. Adding, removing, or changing package versions will invalidate the cache.
 - Changing any contents in the notebook's frontmatter.
 - Changing any contents of any executable Julia cells, including cell options.