Very good grut, I'm happy to see you tackling this head-on. :D
I hope you don't mind some questions and suggestions, you're free to use them or not but I want to let you know at least... here goes:
Your CSS is perfectly valid now except for one minor thing that can cause plenty of problems in browsers, you need to add the hex-decimal prefix (a square: #) in front of hex-colors (#FFFFFF instead of just FFFFFF). Besides that your CSS is looking good. :)
In HTML it can be seen as a personal preference whether you write tags/elements and attributes in uppercase (example: <IMG SRC="path/to/image.ext">) or lowercase (example: <img src="path/to/image.ext">). At some point I think you will want to move towards XHTML however, and in XHTML you must write it in lowercase like in the second example. I would say it's a good practise to do it all in lowercase so that once you move over to newer doctypes, it wont be as much of a big move when it comes to pure habits.
Images, no matter what doctype, should have an alt attribute which is alternative text if the image doesn't load. The html document should actually only contain content related images (as in not design related ones) but we can't be picky on everything here in life, not always at least. You could add something like alt="Design related image" to the design related images and the person viewing would at least know in case it doesn't load.
Now this thing is something I'm just curious about, how come you tab backwards? (backwards compared to how the most of us do it) Tabbing isn't important for the computer but it is for yourself, with proper tabbing it's a lot easier to find missing tags/elements and just to read your code and make out areas in it. :)
<?php // Using the PHP tag as it works with white-space. :)
<parent>
<child-parent>
<child>This is some text inside this 2nd child.</child>
</child-parent>
<child-parent>
<child>This is some text inside this 2nd child.</child>
</child-parent>
</parent>
<parent>
<child-parent>
<child>This is some text inside this 2nd child.</child>
</child-parent>
<child-parent>
<child>This is some text inside this 2nd child.</child>
</child-parent>
</parent>
?>
If that now makes the slightest sense...
I found that your code you use right now has a missing </div>, tabbing like this would have made it easier for you to find it as it becomes more obvious:
<?php // Using the PHP tag as it works with white-space. :)
<parent>
<child-parent>
<child>This is some text inside this 2nd child.</child>
</child-parent>
<child-parent>
<child>This is some text inside this 2nd child.</child>
</child-parent>
</parent>
<parent>
<child-parent>
<child>This is some text inside this 2nd child.</child>
</child-parent>
<child-parent>
<child>This is some text inside this 2nd child.</child>
</child-parent>
?>
(Last </parent> is missing there)
Also, when you can, try to use id="text" instead of name="text". You can't do that all the time (and you shouldn't) but when it is in the subject of giving JavaScripts and CSS targets (#text {} for example) you should use id="text". :)
Lastly, try to (even though it didn't fix your problem like so), add a proper doctype and charset to your code. Here you can see examples of doctypes and here you can get a simple introduction to what those crazy pieces of code really mean and does for you. You could also read this A List Apart article: "Fix Your Site With the Right DOCTYPE!" if you have time some day.
This explains what a charset is and how to use it. No, I don't expect you to start reading all that text, I can point out that this part could be worth trying to read though. (you don't have to do it right now of course) ;)
----
Now, if you have read all this and thought it sounded somewhat reasonable, I wouldn't force you to do all that yourself so I attached a version of your code with the suggested additions and changes, use if it you want:
___________________
Neversidian, your staff is broken.
Last edited by Simon, August 24th, 2005 08:33 AM (Edited 1 times)
August 23rd, 2005 
