Small documentation enhancement and typo fix (#41758)

JuliaLang · Aug 2, 2021 · 4bcdf9d · 4bcdf9d
1 parent 6f29690
commit 4bcdf9d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/doc/src/manual/arrays.md b/doc/src/manual/arrays.md
@@ -875,7 +875,7 @@ full set of cartesian indices to do their lookup (see [`IndexStyle`](@ref) to
 introspect which is which). As such, when iterating over an entire array, it's
 much better to iterate over [`eachindex(A)`](@ref) instead of `1:length(A)`.
 Not only will the former be much faster in cases where `A` is `IndexCartesian`,
-but it will also support OffsetArrays, too.
+but it will also support [OffsetArrays](https://github.com/JuliaArrays/OffsetArrays.jl), too.
 
 #### Omitted and extra indices
 

diff --git a/doc/src/manual/style-guide.md b/doc/src/manual/style-guide.md
@@ -144,7 +144,7 @@ is stated to be the API. This has several benefits:
 - Package developers are freer to change the implementation without breaking
   user code.
 - Methods can be passed to higher-order constructs like [`map`](@ref) (e.g.
-  `map(imag, zs))` rather than `[z.im for z in zs]`).
+  `map(imag, zs)`) rather than `[z.im for z in zs]`).
 - Methods can be defined on abstract types.
 - Methods can describe a conceptual operation that can be shared across
   disparate types (e.g. `real(z)` works on Complex numbers or Quaternions).