From 4d054901eee0ab3ec37b3b7e5bb4aff023cc4d9e Mon Sep 17 00:00:00 2001
From: Rob Larsen <rob@drunkenfist.com>
Date: Tue, 28 Jun 2011 10:59:50 -0400
Subject: [PATCH] text changes from NA to US

---
 index.php             | 2 +-
 sections/general.html | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.php b/index.php
index a8f99596..4a1d40a6 100644
--- a/index.php
+++ b/index.php
@@ -12,7 +12,7 @@
 		<div id="container">
 		
 			<header role="banner">
-				<h1><a id="logo" href="<?php echo $page_root; ?>">Isobar North America</a></h1>
+				<h1><a id="logo" href="<?php echo $page_root; ?>">Isobar US</a></h1>
 				
 				<canvas id="canvas-logo" width="500" height="300">
 					<strong>Your browser cannot handle the awesomeness of this!</strong>
diff --git a/sections/general.html b/sections/general.html
index 30b49df0..0962c983 100644
--- a/sections/general.html
+++ b/sections/general.html
@@ -3,7 +3,7 @@
 
 <h2>Overview</h2>
 
-<p>This document contains guidelines for web applications built by the Creative Technology (front end engineering) practice of Isobar North America (previously Molecular). It is to be readily available to anyone who wishes to check the iterative progress of our best practices. If you have any feedback, please leave a comment on the <a href="http://na.isobar.com/2010/our-front-end-development-best-practices/#comments">announcement blog post</a>.</p>
+<p>This document contains guidelines for web applications built by the Creative Technology (front end engineering) practice of Isobar US. It is to be readily available to anyone who wishes to check the iterative progress of our best practices. If you have any feedback, please leave a comment on the <a href="http://na.isobar.com/2010/our-front-end-development-best-practices/#comments">announcement blog post</a>.</p>
 
 <p>This document's primary motivation is two- fold: <tt>1)</tt> code consistency and <tt>2)</tt> best practices. By maintaining consistency in coding styles and conventions, we can ease the burden of legacy code maintenance, and mitigate risk of breakage in the future. By adhering to best practices, we ensure optimized page loading, performance and maintainable code.</p>