-
-
Notifications
You must be signed in to change notification settings - Fork 684
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V2 chapter texts #2568
Comments
I think these are all solid suggestions. Thumbs up. |
😄 |
Well, the recommendation should not be read out of context :) It has already been said a few lines before ("The standard is helpful for all organizations all over the world but is particularly relevant to US agencies and those dealing with US agencies."). US agencies anyway need to follow it and they don't need to read it from the ASVS. For every other audience, it is just a noise and may make a feeling, that ASVS is US-audience oriented as well. |
I have tried to tidy those up.
Changed it to bold
Removed
Fixed.
Added the § symbol which hopefully makes it clearer.
Tried to clean this up All these changes are here: 9c3f14d |
Even after #2588 is merged, this should stay open for a final review of the text. |
this "little hard to undestand" part should be turned to "is different", or the entire line can be deleted. |
|
Final review changes in #2656 |
##
) title, it would be also helpful and precondition to extract section texts to JSON file, in case we want to solve Machine parseable format does not include informative text #821edit:
The text was updated successfully, but these errors were encountered: