summaryrefslogtreecommitdiff
path: root/taler-developer-manual.rst
diff options
context:
space:
mode:
Diffstat (limited to 'taler-developer-manual.rst')
-rw-r--r--taler-developer-manual.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index 2369c0a7..91bec2b1 100644
--- a/taler-developer-manual.rst
+++ b/taler-developer-manual.rst
@@ -169,7 +169,7 @@ you can add the nightly package sources.
# For Debian (bullseye)
$ echo "deb https://deb.taler.net/apt-nightly bullseye-taler-nightly main" > /etc/apt/sources.list.d/taler.list
- # Both: Install signing key for nightly packages
+ # Both: Install signing key for nightly packages
$ wget -O - https://taler.net/taler-systems-nightly.gpg.key | apt-key add -
@@ -381,7 +381,7 @@ Documentation Builder
All the Taler documentation is built by the user ``docbuilder`` that
runs a Buildbot worker. The following commands set the ``docbuilder`` up,
-starting with a empty home directory.
+starting with an empty home directory.
.. code-block:: console
@@ -403,7 +403,7 @@ Website Builder
Taler Websites, ``www.taler.net`` and ``stage.taler.net``, are built by the
user ``taler-websites`` by the means of a Buildbot worker. The following
-commands set the ``taler-websites`` up, starting with a empty home directory.
+commands set the ``taler-websites`` up, starting with an empty home directory.
.. code-block:: console
@@ -1129,7 +1129,7 @@ This chapter is a VERY ABSTRACT description of how testing is
implemented in Taler, and in NO WAY wants to substitute the reading of
the actual source code by the user.
-In Taler, a test case is a array of ``struct TALER_TESTING_Command``,
+In Taler, a test case is an array of ``struct TALER_TESTING_Command``,
informally referred to as ``CMD``, that is iteratively executed by the
testing interpreter. This latter is transparently initiated by the
testing library.
@@ -1152,7 +1152,7 @@ CMDs: for example, CMD1 may create some key material and CMD2 needs this
key material to encrypt data.
The offering of internal values from CMD1 to CMD2 is made by *traits*. A
-trait is a ``struct TALER_TESTING_Trait``, and each CMD contains a array
+trait is a ``struct TALER_TESTING_Trait``, and each CMD contains an array
of traits, that it offers via the public trait interface to other
commands. The definition and filling of such array happens transparently
to the test developer.