Close, but not 100% true. G1 is for making a controlled move, where the axis all must move with each other and all reach their destination at the same time. It does not have anything to do with the tool, but it is always used with it, because it would not make sense not to.
G0 is also true enough just a travel move, where all axis just should get to their set position as fast as they can, they are not forced to follow each other or limit their speed because of one axis being slower than the others. This is just mostly for very old machines with very large speed difference between their axis, newer ones pretty much just moves as G1, while just ignoring Feed.
@Michael_Andresen I’m aware of the historical meaning, it’s even mentioned in http://smoothieware.org/g0 , but the documentation is about what it means now in Smoothie. Thanks for the comment anyway though.
@Arthur_Wolf very useful. How about the S parameter and how that is used for 3D and lasers?
This would have saved me some learning time and I like that it is smoothie specific.
Perhaps list the levels of firmware these apply to.
Be great to do this with all the G and M codes.
@donkjr Added the S parameter, thanks 
The plan is to do this for all of them, but it’s a huge task. Help welcome.
@Arthur_Wolf ok, give me some to do. What graphics tools, how to review format etc?
@donkjr So, for documenting G-code, the guide is :
- Don’t do the G ones, do the M ones. I’m going to do the G ones with the assistance of other devs, since there are lots of gotchas there. the M ones are simpler.
- Go to the G0 page, click edit, copy the source markup, and create the page for your m-code ( by going to http://smoothieware.org/m1234 for M1234 and clicking on edit ), and paste the source there. Then edit it to fit the right information
- If you need any kind of information, contact me at wolf.arthur@gmail.com
- I’ll go over what you do once it’s done so don’t worry too much about being correct, I’ll fix it. The point is you are enormously reducing the amount of work others have to do.
- Read https://jacobian.org/writing/technical-style/
- We have no specific graphics tools. When I really need to do a diagram, I use inkscape ( at which I suck ) and I commit it to https://github.com/arthurwolf/smoothieboard-graphics which then allows me to get a nice link like http://arthurwolf.github.io/smoothieboard-graphics/schematics/height-adjustment.svg
- Make it interresting
- I generally just steal graphics from other sites by using google images. It’s bad, but someday we’ll be asking volunteer graphic artists to replace them all with original art.
- If you feel like you have graphic artist talents, and can produce clean, professional looking diagrams, I have a shitton of work for you, which is much more important than writing text.
Sounds good ?