diff options
| author | Ruben Kerkhof <ruben@rubenkerkhof.com> | 2019-03-20 20:08:33 +0100 |
|---|---|---|
| committer | Ruben Kerkhof <ruben@rubenkerkhof.com> | 2019-03-20 20:08:33 +0100 |
| commit | 56f0bea71861da9107da86b2e880dadaa64ac52b (patch) | |
| tree | 5a3886a442ba24b780042a5d0b890400607be805 /doc/developer/topotests.rst | |
| parent | Merge pull request #3968 from donaldsharp/bfd_valuable_valgrind (diff) | |
| download | frr-56f0bea71861da9107da86b2e880dadaa64ac52b.tar.xz frr-56f0bea71861da9107da86b2e880dadaa64ac52b.zip | |
doc: fix a couple of typos
Found with https://github.com/codespell-project/codespell
Signed-off-by: Ruben Kerkhof <ruben@rubenkerkhof.com>
Diffstat (limited to 'doc/developer/topotests.rst')
| -rw-r--r-- | doc/developer/topotests.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/developer/topotests.rst b/doc/developer/topotests.rst index aa06c8dff..605b9c9a0 100644 --- a/doc/developer/topotests.rst +++ b/doc/developer/topotests.rst @@ -151,7 +151,7 @@ Collect Memory Leak Information ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ FRR processes have the capabilities to report remaining memory allocations upon -exit. To enable the reporting of the memory, define an enviroment variable +exit. To enable the reporting of the memory, define an environment variable ``TOPOTESTS_CHECK_MEMLEAK`` with the file prefix, i.e.:: export TOPOTESTS_CHECK_MEMLEAK="/home/mydir/memleak_" @@ -410,7 +410,7 @@ Defining the Topology The first step to write a new test is to define the topology. This step can be done in many ways, but the recommended is to use Graphviz to generate a drawing of the topology. It allows us to see the topology graphically and to see the -names of equipments, links and addresses. +names of equipment, links and addresses. Here is an example of Graphviz dot file that generates the template topology :file:`tests/topotests/example-test/test_template.dot` (the inlined code might |