I am no expert in AsciiDoc, so I don't know if I got the formatting correct.

I am no expert in AsciiDoc, so I don't know if I got the formatting correct.

How to check the result is explained in the README:

Run the following commands and open http://localhost:8000/

$ make && make serve

Just looking at the diff, everything looks fine.

Also, the README asks to use semantic linebreaks, so perhaps you should use them?

Note: I am not a member of the Packaging Committee.
In the end, I will not be deciding if this pull request can be merged.
In particular, I have noticed that many changes that do not use semantic linebreaks are merged.

Thanks for the review, @oturpe

Also, the README asks to use semantic linebreaks, so perhaps you should use them?

Originally, I tried to wrap the lines at the 80-characters boundary. Now I added a semantic break after the full stop in the first patch. Is that OK?

Hmm, I don't see any difference.
Is this just Pagure giving me stale data?

Possibly.

Earlier it used to be:

- * Golang source packages MUST be named after their main import path.
+ * Golang source packages dedicated to providing code MUST be named after their
+   main import path. This

Now, it's:

- * Golang source packages MUST be named after their main import path.
+ * Golang source packages dedicated to providing code MUST be named after their
+   main import path.

Ok, I see. I was expecting this:

- * Golang source packages MUST be named after their main import path.
+ * Golang source packages dedicated to providing code MUST be named after their main import path.

I.e. there is no maximum length of a line, they just are as long as they need to be.
And if they get really too long, then it may be that shorter sentences should be used.

However, I am not sure if there is much to gain from iterating this,
seeing that the rest of the page already uses fixed line length style.

Thank you for contributring to the guidelines!

I.e. there is no maximum length of a line, they just are as
long as they need to be. And if they get really too long, then
it may be that shorter sentences should be used.

Aha, ok. I kept the 80-characters boundary because https://sembr.org/ recommended it. I don't have a strong opinion about it.

I have always interpreted that recommendation to mean "please write short sentences" :smile:

ping

Thanks, @tibbs !