guide: move one screenshot to the front page

This used to work with the old asciidoc README.

Change-Id: I974137b53a924972eec55c0e0f579ffa95303302

.github/workflows/tests.yml

@@ -16,7 +16,7 @@ jobs:
     - uses: actions/checkout@v2
     - uses: actions/setup-python@v2
       with:
-        python-version: 3.9
+        python-version: 3.10
     - name: Run make check
       run: |
         tools/ci-build.sh
@@ -32,7 +32,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-python@v2
         with:
-          python-version: 3.9
+          python-version: 3.10
       - name: Run make check
         run: |
           tools/ci-build.sh
@@ -48,7 +48,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-python@v2
         with:
-          python-version: 3.9
+          python-version: 3.10
       - name: Run make pack
         run: |
           tools/ci-build.ps1

guide/src/README.md

@@ -12,6 +12,10 @@ map individuals and families to graph nodes and connections between them to grap
 takes care of the rest. What's unique about `ged2dot` is that it allows more than showing ancestors
 and descendants of a single individual (what you can easily do with random family editor software).
 
+It looks like this:
+
+![screenshot](https://vmiklos.hu/ged2dot/tests/screenshot.png)
+
 ## Contributing
 
 ged2dot is free and open source. You can find the source code on

guide/src/usage.md

@@ -18,9 +18,7 @@ nodes around the root family.
 
 ## Layout
 
-The layout does a Breadth First Search (BFS) traversal on the graph, from the starting family:
-
-![screenshot](https://vmiklos.hu/ged2dot/tests/screenshot.png)
+The layout does a Breadth First Search (BFS) traversal on the graph, from the starting family.
 
 This has several benefits over explicitly trying to guess which family belongs to which generation.
 Some example more tricky cases, which are handled by `ged2dot`: