html {
	margin: 0px; 
	padding: 0px; 
	border: 0px;
	}
.content { /* All the content boxes belong to the content class. */
	background-color: #FFF;
	border: 1px solid #060;
	margin: 0px 1em 20px 1em; 
	_margin: 0px 1em 20px 1em; 
	min-width: 120px; 
	padding: 10px; 
	position: relative;  /* Position is declared "relative" to gain control of stacking order (z-index). */
	width: auto;
	z-index: 4; /* This allows the content to overlap the right menu in narrow windows in good browsers. */
	}
.contentHeader {
	color: white;
	background-color: #060;
	margin-top: 0px;
	margin-right: 0px;
	margin-left: 0px;
	padding: .5em;
	}

#leftNav {
	position: absolute;
	width: 21em;
	top: 150px;
	left: 0px;
	z-index: 3;
/* Here is the ugly brilliant hack that protects IE5/Win from its own stupidity. Thanks to Tantek Celik for the hack and to Eric Costello for publicizing it. IE5/Win incorrectly parses the "\"}"" value, prematurely closing the style declaration. The incorrect value, for IE5/Win, is above, while the correct value is below. See http://glish.com/css/hacks.asp for details. */
	voice-family: "\"}\"";
	voice-family:inherit;
	width:16em;
	}
/* I've heard this called the "be nice to Opera 5" rule. Basically, it feeds correct length values to user agents that exhibit the parsing error exploited above yet get the CSS box model right and understand the CSS2 parent-child selector. ALWAYS include a "be nice to Opera 5" rule every time you use the Tantek Celik hack (above). */
body>#leftNav {width: 16em;}

#leftNav a {
	color: #FFF;
	padding: 0px .3em 0px .3em;
	}
#leftNav a:hover {
	color: #F00;
	padding: 0px .3em 0px .3em;
	}
	
#rightNav {
	font-size: 12px;
	top: 20px;
	left: 3px;
	border: 0px solid #060;
	background-color: white;
	position: absolute;
	width: 16em;
	z-index: 2;
	}

}