wiki: say topology where a topology is meant, and stop saying scenario scenario is netroub's word - a configuration together with the events that happen in it, defined in its papers and in its own schema, where a scenario is a topology plus events. This documentation had taken it for what a reader writes, which would have left two projects by the same author using one word for two things. What you write - the DOT file and the YAML that configures it - is a topology, which is how this field already speaks: containerlab calls its own file a topology definition and puts the nodes' images and configuration in it. Basic-Concepts and Home say so before the word is used. Where only the graph is meant the pages now say the DOT file, and topology file is left to mean what a platform reads.
wiki: say what each module is for, and run labs through the entry script The module list mixed a platform with a configuration helper without saying so. Modules are now introduced by what they do for you: platform modules write the file their platform reads, which is where the automation is; software modules help write what runs inside the nodes; assert checks the scenario against itself. Writing a module is a different subject from using one, so the interfaces and their timing moved to a page of their own, along with what a module may and may not say to a scenario. Each platform page now runs its lab through the generated script first and by hand second. That is not a preference: destroy through the script runs the teardown commands, collects the files, and cleans up what the lab left on the machine, and none of it happens when the platform's own command is called directly.