Skip to content

Commit

Permalink
Fix formatting of inline code samples which are pluralized
Browse files Browse the repository at this point in the history
  • Loading branch information
suzannehamilton authored and harrah committed Feb 6, 2014
1 parent 825bf87 commit 76df886
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
6 changes: 3 additions & 3 deletions src/sphinx/Getting-Started/Basic-Def.rst
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ becomes sbt's new map.
To create its map, sbt first sorts the list of settings so that all
changes to the same key are made together, and values that depend on
other keys are processed after the keys they depend on. Then sbt walks
over the sorted list of `Setting` and applies each one to the map in
over the sorted list of `Setting`\ s and applies each one to the map in
turn.

Summary: A build definition defines a list of `Setting[T]`, where a
Expand Down Expand Up @@ -82,8 +82,8 @@ A `build.sbt` file is a list of `Setting`, separated by blank lines.
Each `Setting` is defined with a Scala expression.
The expressions in `build.sbt` are independent of one another, and
they are expressions, rather than complete Scala statements. These
expressions may be interspersed with `val`s, `lazy val`s, and `def`s,
but top-level `object`s and classes are not allowed in `build.sbt`.
expressions may be interspersed with `val`\ s, `lazy val`\ s, and `def`\ s.
Top-level `object`\ s and `class`\ es are not allowed in `build.sbt`.
Those should go in the `project/` directory as full Scala source files.

On the left, :key:`name`, :key:`version`, and :key:`scalaVersion` are *keys*. A
Expand Down
2 changes: 1 addition & 1 deletion src/sphinx/Howto/runningcommands.rst
Original file line number Diff line number Diff line change
Expand Up @@ -84,5 +84,5 @@ For example,
> eval 2+2
4: Int
Variables defined by an `eval` are not visible to subsequent `eval`s, although changes to system properties persist and affect the JVM that is running sbt.
Variables defined by an `eval` are not visible to subsequent `eval`\ s, although changes to system properties persist and affect the JVM that is running sbt.
Use the Scala REPL (:key:`console` and related commands) for full support for evaluating Scala code interactively.

0 comments on commit 76df886

Please sign in to comment.