One of the problems I have with a great deal of product documentation is when the author has a number of underlying assumptions ... One of the things which makes me very good at QA and documentation is my ability to think like a noob ... which in this case, I actually am ...
The problem comes in the documentation's underlying assumptions regarding the user's understanding of Linux and its installation requirements and standards.
I wasn't aware that I needed a separate partition for the boot and the home directories, so I only made one partition with a mount-point of \ ... I also wasn't aware that I needed to specify things regarding grub2 in the bottom section of the screen. After a bit of trial and error, I figured out that I needed a separate /boot and /home partition and mount- point, along with having the swap on yet another partition. I think I also did a third /usr mount-point, but can't recall for sure at the moment. I then also told Grub2 where to go -- the C drive. Installation ran fin then and everything is happy.
Now the fun part is figuring out Linux file extensions, how to use apps, and some rather tedious security and installation issues. For example, I downloaded the LInux JRE as I need to install the most recent. I have tried 3 different package managers so far, and none of them want to help me install Java and none of them list the true Oracle JRE as an installable option - just the openJRE and such, which are not as current. I wasn't aware of LibreOffice and also was trying ot install OpenOffice. Following the instructions they provided were simply in error. Such as with OpenOffice, it tells you to unzip (tar z... xxx) the package and then there is supposed to be a specific directory structure created. I used copy paste to avoid typo's so I KNOW that I executed the command *EXACTLY* as instructed, but the _OO* directory wasn't created. Instead there was one that was something EN (obviously "English") and then under there were 3 more, DEB and two others. OpenOffice's directions didn't mention these directories or how to address them and what files needed to be used. Instead the user is pointed off into la-la land. I am sure to you old hands that it is of no challenge, but to me, it was frustratingly insurmountable. On top of that, none of the package installers which came with Mint seemed to want to be of searvice and all refused to acknowledge the existence of the software. I decided that then was a good time to do some comparisons of OpenOffice vs. LibreOffice. Java is still not installed.
When writing instructions for such things, you can't just say "run the install logged on as root" for example. Uh, what's root and how do I log on as it? What is the install [file] and how do I run it? I at least had a bit of a clue on the root logon, knowing root referenced essentially the admin, but didn't know how to actually do it. On Windows, that's easy, right click on the command prompt icon and choose "run as administrator" ... There were a number of issues like that where a level of knowledge was assumed which should not be when dealing with a product hyped as being particularly well-suited for noobs.
I suppose that as I embark on this journey I should keep a log of all the little things like this which will cause a neophyte issues, and could probably turn them into a book ...