docs: Minor corrections, related to the alias removals
Fixed up the documentation language here and there, related to the alias removals in previous commits. Signed-off-by: Gergely Nagy <algernon@madhouse-project.org>
This commit is contained in:
parent
8e2a892469
commit
dee02c5928
@ -17,7 +17,7 @@ Macros
|
||||
defn-alias
|
||||
------------------------
|
||||
|
||||
The ``defn-alias`` and macro is much like `defn`_,
|
||||
The ``defn-alias`` macro is much like ``defn``,
|
||||
with the distinction that instead of defining a function with a single
|
||||
name, these can also define aliases. Other than taking a list of
|
||||
symbols for function names as the first parameter, ``defn-alias``
|
||||
|
@ -842,7 +842,7 @@ lif and lif-not
|
||||
.. versionadded:: 0.11.0
|
||||
lif-not
|
||||
|
||||
For those that prefer a more Lispy ``if`` clause, we have, or
|
||||
For those that prefer a more Lispy ``if`` clause, we have
|
||||
``lif``. This *only* considers ``None`` / ``nil`` to be false! All other
|
||||
"false-ish" Python values are considered true. Conversely, we have
|
||||
``lif-not`` in parallel to ``if`` and ``if-not`` which
|
||||
@ -1223,7 +1223,7 @@ counted starting from the end of the list. Some example usage:
|
||||
raise
|
||||
-------------
|
||||
|
||||
The or ``raise`` forms can be used to raise an ``Exception`` at
|
||||
The ``raise`` form can be used to raise an ``Exception`` at
|
||||
runtime. Example usage:
|
||||
|
||||
.. code-block:: clj
|
||||
|
Loading…
x
Reference in New Issue
Block a user