Skip to content

Commit 196956d

Browse files
authored
Replace julia with Julia in faq when referring to the language. (#50103)
1 parent 1177b54 commit 196956d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/src/manual/faq.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ On the other hand, language *interoperability* is extremely useful: we want to e
2222

2323
### How does Julia define its public API?
2424

25-
The only interfaces that are stable with respect to [SemVer](https://semver.org/) of `julia`
25+
The only interfaces that are stable with respect to [SemVer](https://semver.org/) of Julia
2626
version are the Julia `Base` and standard libraries interfaces described in
2727
[the documentation](https://docs.julialang.org/) and not marked as unstable (e.g.,
2828
experimental and internal). Functions, types, and constants are not part of the public
@@ -36,8 +36,8 @@ a complex non-public API, especially when using it from a stable package, it is
3636
to open an [issue](https://github.com/JuliaLang/julia/issues) or
3737
[pull request](https://github.com/JuliaLang/julia/pulls) to start a discussion for turning it
3838
into a public API. However, we do not discourage the attempt to create packages that expose
39-
stable public interfaces while relying on non-public implementation details of `julia` and
40-
buffering the differences across different `julia` versions.
39+
stable public interfaces while relying on non-public implementation details of Julia and
40+
buffering the differences across different Julia versions.
4141

4242
### The documentation is not accurate enough. Can I rely on the existing behavior?
4343

0 commit comments

Comments
 (0)