Unfortunately, the Look Inside the Book ("LITB", also sometimes written as "LookInsideTheBook") functionality at Amazon (and at Nook, iBooks, etc., as it happens) is not the same programming as the eBooks and eBook readers themselves.  Nor does Amazon make the LITB coding public, and it provides us and you with no place where we can test how the LITB will appear, before you publish the book.

We do the best we can, to ensure that your LITB looks awesome—but we can't truly know, pre-publication, how it will appear.  If something goes amiss with the LITB, contact us right away. We'll do what we can to fix it, but again—that may mean that you have to upload and re-upload new files, and publish them, for us to test the final appearance for your book.

The Reality of "Fixing" the LookInsideTheBook (LITB)

The challenge is, while there are some things we can do about the Look Inside The Book there are many things that we can't fix. For example, most embedded body fonts won't display, at the LITB.  This is because Amazon wants all the books to display in Georgia, the now-default font for Kindle eBooks.  If we use a different body font, typically, it's fine, but in some instances, weird and unpleasant things can happen, usually around ligatures.  (If you don't know what typographical ligatures are, they are letters in a font set that work together, like "ff" or "ft" or "lf," etc.  They exist as single coded entities, rather than separate letters. This isn't the time or place for a lecture on ligatures, but suffice to say that in certain circumstances, ligature characters can disappear from within the LITB at Amazon!  Bad!)