Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos/formatting in TextFormatting.rst #212

Merged
merged 1 commit into from
Dec 4, 2015
Merged

Fix typos/formatting in TextFormatting.rst #212

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions docs/TextFormatting.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,8 +129,7 @@ Debug Printing

Via compiler magic, *everything* conforms to the ``CustomDebugStringConvertible``
protocol. To change the debug representation for a type, you don't
need to declare conformance: simply give the type a ``debugFormat()``
::
need to declare conformance: simply give the type a ``debugFormat()``::

/// \brief A thing that can be printed in the REPL and the Debugger
protocol CustomDebugStringConvertible {
Expand Down Expand Up @@ -199,7 +198,7 @@ Because it's not always efficient to construct a ``String``
representation before writing an object to a stream, we provide a
``Streamable`` protocol, for types that can write themselves into an
``OutputStream``. Every ``Streamable`` is also a ``CustomStringConvertible``,
naturally ::
naturally::

protocol Streamable : CustomStringConvertible {
func writeTo<T: OutputStream>(target: [inout] T)
Expand Down Expand Up @@ -426,7 +425,7 @@ would also make ``OutputStream`` adapters a *bit* simpler to use
because you'd never need to “write back” explicitly onto the target
stream. However, stateful ``OutputStream`` adapters would still need a
``close()`` method, which makes a perfect place to return a copy of
the underlying stream, which can then be “written back.” :
the underlying stream, which can then be “written back”:

.. parsed-literal::

Expand Down