lulu-berlin/lix
0
0
Fork 0
forked from lix-project/lix
Code Pull requests Activity

Fix typos

Browse source
This commit is contained in:
Eelco Dolstra 2014-03-11 13:16:21 +01:00
parent 2f2a20ed18
commit 92a848f674
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/manual/release-notes.xml
View file

@ -26,8 +26,8 @@
case where the attribute name is just a single antiquotation, case where the attribute name is just a single antiquotation,
the quotes can be dropped (e.g. the above example can be written the quotes can be dropped (e.g. the above example can be written
<literal>set.${foo}</literal>). If an attribute name inside of a <literal>set.${foo}</literal>). If an attribute name inside of a
set declaration evaluates to <literal>"${null}"</literal> (e.g. set declaration evaluates to <literal>null</literal> (e.g.
<literal>{ ${null} = false; }</literal>), then that attribute is not added <literal>{ ${null} = false; }</literal>), then that attribute is not
added to the set.</para></listitem> added to the set.</para></listitem>
</itemizedlist> </itemizedlist>

2
doc/manual/writing-nix-expressions.xml
View file

@ -872,7 +872,7 @@ coerced to a string and <literal>456</literal> otherwise (again
assuming <literal>bar</literal> is antiquotable).</para> assuming <literal>bar</literal> is antiquotable).</para>
<para>In the special case where an attribute name inside of a set declaration <para>In the special case where an attribute name inside of a set declaration
evaluates to <literal>"${null}"</literal> (which is normally an error, as evaluates to <literal>null</literal> (which is normally an error, as
<literal>null</literal> is not antiquotable), that attribute is simply not <literal>null</literal> is not antiquotable), that attribute is simply not
added to the set: added to the set: