Merge pull request #366 from sblauth/docs/fix_xdmf_loading

Fix the docs at demos/documented/misc/xdmf_io/demo_xdmf_io

demos/documented/misc/xdmf_io/demo_xdmf_io.py

@@ -53,7 +53,8 @@
 # This means, that when we now use cashocs to solve the problem, the output is stored to
 # a directory, which is specified in the {ini}`result_dir` of the Output Section of the
 # config file. As we have not specified a directory, the files will be created in the
-# default location `./results`, and the XDMF files will be stored in `./results/xdmf`.
+# default location `./results`, and the XDMF files will be stored in
+# `./results/checkpoints`.
 #
 # The code for solving the problem is as follows
 
@@ -83,8 +84,8 @@
 sop.solve()
 # -
 
-# After we have run this code, we can see that now a directory `./results` exists and
-# that the XDMF files are located in `./results/xdmf`, as expected.
+# After we have run this code, we can see that now a directory `./results`
+# exists and that the XDMF files are located in `./results/checkpoints`, as expected.
 #
 # ### Reading the XDMF files back into python
 #
@@ -111,7 +112,7 @@
 # <demo_multiple_variables>` or problems with {ref}`mixed spaces
 # <demo_monolithic_problems>`, the outputs could, e.g., have the names
 # {python}`'state_1_2.xdmf'`, so that the corresponding name would be
-# {python}`'state_1_2'`
+# {python}`'state_1_sub_2'`
 # :::
 #
 # :::{warning}