2 new revisions:

Revision: 0de04ac12f05
Branch:   default
Author:   Anssi Syrjäsalo
Date:     Mon Jun 10 07:47:49 2013
Log:      Fixed typos in named arguments documentation in User Guide....
http://code.google.com/p/robotframework/source/detail?r=0de04ac12f05

Revision: 1510b78de11a
Branch:   default
Author:   Anssi Syrjäsalo
Date:     Mon Jun 10 07:48:13 2013
Log:      regen
http://code.google.com/p/robotframework/source/detail?r=1510b78de11a

==============================================================================
Revision: 0de04ac12f05
Branch:   default
Author:   Anssi Syrjäsalo
Date:     Mon Jun 10 07:47:49 2013
Log:      Fixed typos in named arguments documentation in User Guide.

Update issue 1430

Proofread and fixed a couple of typos.
http://code.google.com/p/robotframework/source/detail?r=0de04ac12f05

Modified:
 /doc/userguide/src/CreatingTestData/CreatingTestCases.rst
 /doc/userguide/src/ExtendingRobotFramework/CreatingTestLibraries.rst

=======================================
--- /doc/userguide/src/CreatingTestData/CreatingTestCases.rst Sun Jun 9 07:00:51 2013 +++ /doc/userguide/src/CreatingTestData/CreatingTestCases.rst Mon Jun 10 07:47:49 2013
@@ -264,7 +264,7 @@
 Starting from Robot Framework 2.8 this causes an explicit error.
 Otherwise the order of the named arguments does not matter.

-.. note:: Prior to Robot Framework 2.8 it was not possible name arguments
+.. note:: Prior to Robot Framework 2.8 it was not possible to name arguments
           that did not have a default value.

 Escaping named arguments syntax
@@ -292,7 +292,7 @@

Naming arguments is supported by `user keywords`_ and by most `test libraries`_. The only exception are Java based libraries that use the `static library API`_.
-Library documentation generated with `Libdoc`_ has a note does the library
+Library documentation generated with `Libdoc`_ has a note, does the library
 support named arguments or not.

 .. note:: Prior to Robot Framework 2.8 named argument syntax did not work
@@ -339,7 +339,7 @@

Robot Framework 2.8 added a possibility to use the named argument syntax with
 Python keywords that accept `keyword arguments`__ in form :code:`**kwargs`.
-If a keyword uses this syntax , all arguments at the end of the keyword
+If a keyword uses this syntax, all arguments at the end of the keyword
call using the :code:`name=value` syntax, but not matching any other arguments,
 are passed to it as free keyword arguments.

=======================================
--- /doc/userguide/src/ExtendingRobotFramework/CreatingTestLibraries.rst Sun Jun 9 07:00:51 2013 +++ /doc/userguide/src/ExtendingRobotFramework/CreatingTestLibraries.rst Mon Jun 10 07:47:49 2013
@@ -719,7 +719,7 @@
 is only available with Python based libraries.

 If you are already familiar how kwargs work with Python, understanding how
-they works with Robot Framework test libraries is rather simple. The example
+they work with Robot Framework test libraries is rather simple. The example
 below shows the basic functionality.

 .. sourcecode:: python

==============================================================================
Revision: 1510b78de11a
Branch:   default
Author:   Anssi Syrjäsalo
Date:     Mon Jun 10 07:48:13 2013
Log:      regen
http://code.google.com/p/robotframework/source/detail?r=1510b78de11a

Modified:
 /doc/userguide/RobotFrameworkUserGuide.html

=======================================
--- /doc/userguide/RobotFrameworkUserGuide.html Sun Jun  9 07:01:06 2013
+++ /doc/userguide/RobotFrameworkUserGuide.html Mon Jun 10 07:48:13 2013
@@ -2942,7 +2942,7 @@
 Otherwise the order of the named arguments does not matter.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
-<p class="last">Prior to Robot Framework 2.8 it was not possible name arguments +<p class="last">Prior to Robot Framework 2.8 it was not possible to name arguments
 that did not have a default value.</p>
 </div>
 </div>
@@ -2965,7 +2965,7 @@
addition to that, it also works when <a class="reference internal" href="#taking-test-libraries-into-use">taking test libraries into use</a>.</p> <p>Naming arguments is supported by <a class="reference internal" href="#creating-user-keywords">user keywords</a> and by most <a class="reference internal" href="#using-test-libraries">test libraries</a>. The only exception are Java based libraries that use the <a class="reference internal" href="#creating-static-keywords">static library API</a>. -Library documentation generated with <a class="reference internal" href="#libdoc">Libdoc</a> has a note does the library +Library documentation generated with <a class="reference internal" href="#libdoc">Libdoc</a> has a note, does the library
 support named arguments or not.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
@@ -3074,7 +3074,7 @@
 <h4><a class="toc-backref" href="#id419">Free keyword arguments</a></h4>
<p>Robot Framework 2.8 added a possibility to use the named argument syntax with Python keywords that accept <a class="reference external" href="http://docs.python.org/2/tutorial/controlflow.html#keyword-arguments";>keyword arguments</a> in form <span class="code">**kwargs</span>.
-If a keyword uses this syntax , all arguments at the end of the keyword
+If a keyword uses this syntax, all arguments at the end of the keyword
call using the <span class="code">name=value</span> syntax, but not matching any other arguments,
 are passed to it as free keyword arguments.</p>
 <p>For a real life example of using kwargs, let's take a look at
@@ -12615,7 +12615,7 @@
Because Java does not have similar keyword argument concept, this functionality
 is only available with Python based libraries.</p>
<p>If you are already familiar how kwargs work with Python, understanding how -they works with Robot Framework test libraries is rather simple. The example
+they work with Robot Framework test libraries is rather simple. The example
 below shows the basic functionality.</p>
<div class="highlight"><pre><span class="k">def</span> <span class="nf">example_keyword</span><span class="p">(</span><span class="o">**</span><span class="n">stuff</span><span class="p">):</span> <span class="k">for</span> <span class="n">name</span><span class="p">,</span> <span class="n">value</span> <span class="ow">in</span> <span class="n">stuff</span><span class="o">.</span><span class="n">items</span><span class="p">():</span>
@@ -15504,7 +15504,7 @@
 <div class="section" id="linking-to-custom-sections">
 <h5>Linking to custom sections</h5>
<p>Starting from version 2.7.5, Robot Framework's <a class="reference internal" href="#id304">documentation syntax</a> -supports custom <a class="reference internal" href="#section-titles">section titles</a>. The first level titles used in the +supports custom <a class="reference internal" href="#section-titles">section titles</a>, and the titles used in the
 library or resource file introduction automatically create link
 targets. The example below illustrates linking both to automatic and
 custom sections:</p>
@@ -15530,6 +15530,11 @@
<p class="last">Linking to custom sections works only when using <a class="reference internal" href="#robot-framework-documentation-format">Robot Framework
 documentation format</a>.</p>
 </div>
+<div class="note">
+<p class="first admonition-title">Note</p>
+<p class="last">Prior to Robot Framework 2.8, only the first level section
+titles were linkable.</p>
+</div>
 </div>
 <div class="section" id="argument-formatting">
 <h5>Argument formatting</h5>
@@ -17054,7 +17059,7 @@
 <div class="footer">
 <hr class="footer" />
<p>Generated by <a class="reference external" href="http://docutils.sourceforge.net/rst.html";>reStructuredText</a>. Syntax highlighting by <a class="reference external" href="http://pygments.org/";>Pygments</a>.</p>
-<p>Generated on: 2013-06-09 14:01 UTC.
+<p>Generated on: 2013-06-10 14:48 UTC.
 </p>

 </div>

--

--- You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to