Question on Schematic to VHDL conversion.

UNderstanding schematics and moving to HDLs is a good step. Some of the more common HDL mistakes I see are from people that have no concept of the underlying hardware and just write behavioral code. You'll be moving from the other direction, and though at times might write stuff too structural, it tends to be stuff that you understand and that works.

That being said, I would not rely on the schematic to HDL conversions too much. It's possible to have a wire that has no name on it, and so the conversion has to make something up, where in an HDL everything that exists has a name, so that isn't a problem. If anything, get an HDL book or look at examples on the web. It will be a much better training.

I also believe you're going with the "I know what this schematic does, so what does it look like in HDL". Machine-generated HDL is usually pretty ugly and not the goal to achieve. If you have a simulation/testbench, probably the best thing to do is to try writing the HDL from scratch that mimics the schematic. If you can do that, you'll be learning at a good pace. (And don't forget to use the RTL Viewer a lot, which will give you a visual representation, i.e. schematic, of the HDL you're writing...)