Hi,
It starts to look better, thanks again. It's a slow process, I know, but bear with us ;)
For the project as a whole, all samples are intended to be quite ordered/categorised. So the example from Nishant fit in quite well -> JSP -> Lifecycle methods. Meaning it demonstrates a single concept.
With the "learning servlet" it's less clear from its name. In the bigger picture of the project, with dozens of Servlet examples, what does a "learning Servlet" practically mean? All examples are to learn from, and to demonstrate something is working on a specific Servlet implementation (this last part should not be forgotten).
In this case, it's a Servlet to which some simple requests are done via an .html file, where the tests use that .html file as well. Maybe "basicRequests" or "simpleRequests" would be a better name?
Where maybe "simple servlet" didn't fully describe the purpose of the example either, but I think it's still a little bit clearer than "learning servlet".
Also, there's a lot of comments about how basic things work that are not necessarily related to what the sample is demonstrating. We could perhaps say that this is the initial sample everyone should look at, so that one has all those comments, but then we'd better put that in the readme.md. Otherwise it looks quite out of place if say 100 samples only have comments about what they are demonstrating, and then one random sample has comments explaining Maven, Java etc itself
TLDR; consider a better name for the "learning servlet", put in the readme.md that this sample is the initial one people could look at.
Hope this helps ;)
Kind regards,
Arjan Tijms