Code formatting and code consistency review

[ruebot]

We should go through all the examples in current and make sure all the formatting is consistent; consistent variable naming, examples inputs/outputs, and indentation.

@lintool @ianmilligan1 @SamFritz let me know if there is anything else here we should flag.

[ianmilligan1]

I think throughout maybe just making it a straightforward call to example.arc.gz which they can curl down. We've got a mixture of example.arc.gz, example.warc.gz and then path to the example files in the AUT repo. Not sure how best to highlight the curling of example.arc.gz given our new doc structure tho.

[ruebot]

Not all of the examples will work on the example.arc.gz or example.warc.gz files that are in src/test. My thinking here is that it should just be /path/to/web/archives/.

[ianmilligan1]

Yeah I can see pros and cons for both (cut-and-paste works out of the box to see sample output on the former; but how often will people really be testing stuff out on the tiny example (W)ARC... 🤔