We are trying to verify the integrity of an ISO file
We do that by verifying the checksum for the ISO file
OP's Screenshots, in order, show:
The frustrating and condescending message the she received when she tried to look up further instructions for this step in the Ubuntu documentation pages. This links you to:
What seems to be the beginning of the Ubuntu install guide??? From which you can choose your specific use case, i.e. WSL, which then links you to:
The place where it tells you to run the command in question - which seems to be a page where it is telling you to install Ubuntu, NOT a page telling you how to verify the checksums on individual software packets you might have downloaded in order to do so? Which... if you're non-tech-y, and you're worried about possibly bricking your one and only computer because you ran an unverified program that might be a virus or broken somehow (damaged/missing packets - not that you, a non-tech-savvy person, would know that) you are probably ready to give up by this point? Also, if you have the individual install files and not the singular Ubuntu file referenced in that command line, that command would fail anyway, would it not???
A screenshot that indicates a list of places to download the ISO files in question [cut off, but presumably listed below] and links you to a how-to for burning the images to a disk
A screenshot that tells you that you need to verify the ISO integrity, and then apparently (per OP) links you to how to do that in Ubuntu... the thing that you don't have installed...
Like. Okay. Is there a world in which downloading that specific file packet (Ubuntu 24.04) and running that specific command (wsl --install Ubuntu-24.04) bypasses the need for all of this, because it simply installs Ubuntu, this verifying checksums as part of the process? I mean, sure, maybe. But at no point in any of those screenshots does it say anything like "running 'wsl --install -Unbuntu 24.04' will verify checksums as part of the process"; so to me, it in fact does NOT say that in the screenshots. At best that's something that you read into the instructions with outside knowledge that you have, that the non-tech set that this stream was directed at do not have. That's absolutely going to scare them off!
And also, what else does that do? Does it, for instance, uninstall or otherwise render unusable the Windows OS that OP seems to be trying to leave intact, for non-techy users who are just trying to get their feet wet with Linux? Because if so, that's a perfect deliberation of why non-tech people hate tech people, and also why OP has the job that she does.
Also, there's two methods for installing Ubuntu shown in that screenshot. It's late, and I'm sick again, and very tired, but in my experience, often - not always, but often - when there's two methods to do something, there's a possibility that one of the methods accomplishes something different than the other method; you can't simply mix and match unless you understand both pretty in depth. If you are a non-tech person trying to follow these directions, you are barely following the tech jargon in these screenshots. The last thing you want to do is guess and be wrong and fuck up your entire computer. You are not going to knowingly follow instructions from Method A when you are supposed to be following Method B unless you are an idiot, because then when you take your computer to Geek nephew or Geek Squad, they're going to look at you and be like "well why didn't you just follow the instructions?" And I know this, because I've had to rewrite tech instructions on the fly for people in my real life at my real job because the engineers just assumed that Everybody Knew Stuff that Everybody Did Not Know.
All of which is to say. No. It doesn't say that. Those words may be literally printed on the screenshot in one of those screenshots, but it literally does not say to run that specific command line to verify a checksum anywhere that I can see anywhere in those screenshots, and this is why people hate tech people.