changed your-site.com to example.com doc-wide

5 files changed, 20 insertions, 20 deletions

diff --git a/user_guide/general/controllers.html b/user_guide/general/controllers.html
index 034f1b23c..6f568d49e 100644
--- a/user_guide/general/controllers.html
+++ b/user_guide/general/controllers.html
@@ -82,7 +82,7 @@ Controllers
 

 <p>Consider this URI:</p>

 

-<code>www.your-site.com/index.php/<var>blog</var>/</code>

+<code>example.com/index.php/<var>blog</var>/</code>

 

 <p>In the above example, CodeIgniter would attempt to find a controller named <dfn>blog.php</dfn> and load it.</p>

 

@@ -112,7 +112,7 @@ class Blog extends Controller {
 

 <p>Now visit the your site using a URL similar to this:</p>

 

-<code>www.your-site.com/index.php/<var>blog</var>/</code>

+<code>example.com/index.php/<var>blog</var>/</code>

 

 <p>If you did it right, you should see <samp>Hello World!</samp>.</p>

 

@@ -142,7 +142,7 @@ class <var>blog</var> extends Controller {<br />
 <p>In the above example the function name is <dfn>index()</dfn>.  The "index" function is always loaded by default if the

 <strong>second segment</strong> of the URI is empty.  Another way to show your "Hello World" message would be this:</p>

 

-<code>www.your-site.com/index.php/<var>blog</var>/<samp>index</samp>/</code>

+<code>example.com/index.php/<var>blog</var>/<samp>index</samp>/</code>

 

 <p><strong>The second segment of the URI determines which function in the controller gets called.</strong></p>

 

@@ -168,7 +168,7 @@ class Blog extends Controller {
 

 <p>Now load the following URL to see the <dfn>comment</dfn> function:</p>

 

-<code>www.your-site.com/index.php/<var>blog</var>/<samp>comments</samp>/</code>

+<code>example.com/index.php/<var>blog</var>/<samp>comments</samp>/</code>

 

 <p>You should see your new message.</p>

 

@@ -179,7 +179,7 @@ class Blog extends Controller {
 

 <p>For example, lets say you have a URI like this:</p>

 

-<code>www.your-site.com/index.php/<var>products</var>/<samp>shoes</samp>/<kbd>sandals</kbd>/<dfn>123</dfn></code>

+<code>example.com/index.php/<var>products</var>/<samp>shoes</samp>/<kbd>sandals</kbd>/<dfn>123</dfn></code>

 

 <p>Your function will be passed URI segments 3 and 4 ("sandals" and "123"):</p>

 

@@ -287,7 +287,7 @@ function _utility()<br />
 

 <p>Trying to access it via the URL, like this, will not work:</p>

 

-<code>www.your-site.com/index.php/<var>blog</var>/<samp>_utility</samp>/</code>

+<code>example.com/index.php/<var>blog</var>/<samp>_utility</samp>/</code>

 

 

 

@@ -305,7 +305,7 @@ located here:</p>
 

 <p>To call the above controller your URI will look something like this:</p>

 

-<code>www.your-site.com/index.php/products/shoes/show/123</code>

+<code>example.com/index.php/products/shoes/show/123</code>

 

 <p>Each of your sub-folders may contain a default controller which will be

 called if the URL contains only the sub-folder.  Simply name your default controller as specified in your

diff --git a/user_guide/general/routing.html b/user_guide/general/routing.html
index b282e18d8..f3e7995a8 100644
--- a/user_guide/general/routing.html
+++ b/user_guide/general/routing.html
@@ -60,7 +60,7 @@ URI Routing
 <p>Typically there is a one-to-one relationship between a URL string and its corresponding controller class/method.

 The segments in a URI normally follow this pattern:</p>

 

-<code>www.your-site.com/<dfn>class</dfn>/<samp>function</samp>/<var>id</var>/</code>

+<code>example.com/<dfn>class</dfn>/<samp>function</samp>/<var>id</var>/</code>

 

 <p>In some instances, however, you may want to remap this relationship so that a different class/function can be called

 instead of the one corresponding to the URL.</p>

@@ -68,10 +68,10 @@ instead of the one corresponding to the URL.</p>
 <p>For example, lets say you want your URLs to have this prototype:</p>

 

 <p>

-www.your-site.com/product/1/<br />

-www.your-site.com/product/2/<br />

-www.your-site.com/product/3/<br />

-www.your-site.com/product/4/

+example.com/product/1/<br />

+example.com/product/2/<br />

+example.com/product/3/<br />

+example.com/product/4/

 </p>

 

 <p>Normally the second segment of the URL is reserved for the function name, but in the example above it instead has a product ID.

diff --git a/user_guide/general/scaffolding.html b/user_guide/general/scaffolding.html
index 417cb1005..14eed1718 100644
--- a/user_guide/general/scaffolding.html
+++ b/user_guide/general/scaffolding.html
@@ -113,12 +113,12 @@ class Blog extends Controller {<br />
 

 <p>Once you've initialized scaffolding, you will access it with this URL prototype:</p>

 

-<code>www.your-site.com/index.php/<var>class</var>/<dfn>secret_word</dfn>/</code>

+<code>example.com/index.php/<var>class</var>/<dfn>secret_word</dfn>/</code>

 

 <p>For example, using a controller named <var>Blog</var>, and <dfn>abracadabra</dfn> as the secret word,

 you would access scaffolding like this:</p>

 

-<code>www.your-site.com/index.php/<var>blog</var>/<dfn>abracadabra</dfn>/</code>

+<code>example.com/index.php/<var>blog</var>/<dfn>abracadabra</dfn>/</code>

 

 <p>The scaffolding interface should be self-explanatory.  You can add, edit or delete records.</p>

 

diff --git a/user_guide/general/urls.html b/user_guide/general/urls.html
index 9230f98c8..bbfd009ce 100644
--- a/user_guide/general/urls.html
+++ b/user_guide/general/urls.html
@@ -61,7 +61,7 @@ URLS
 <p>By default, URLs in CodeIgniter are designed to be search-engine and human friendly.  Rather than using the standard "query string"

 approach to URLs that is synonymous with dynamic systems, CodeIgniter uses a <strong>segment-based</strong> approach:</p>

 

-<code>www.your-site.com/<var>news</var>/<dfn>article</dfn>/<samp>my_article</samp></code>

+<code>example.com/<var>news</var>/<dfn>article</dfn>/<samp>my_article</samp></code>

 

 <p class="important"><strong>Note:</strong> Query string URLs can be optionally enabled, as described below.</p>

 

@@ -69,7 +69,7 @@ approach to URLs that is synonymous with dynamic systems, CodeIgniter uses a <st
 

 <p>The segments in the URL, in following with the Model-View-Controller approach, usually represent:</p>

 

-<code>www.your-site.com/<var>class</var>/<dfn>function</dfn>/<samp>ID</samp></code>

+<code>example.com/<var>class</var>/<dfn>function</dfn>/<samp>ID</samp></code>

 

 <ol>

 <li>The first segment represents the controller <strong>class</strong> that should be invoked.</li>

@@ -87,7 +87,7 @@ contain functions that make it easy to work with your URI data.  In addition, yo
 

 <p>By default, the <strong>index.php</strong> file will be included in your URLs:</p>

 

-<code>www.your-site.com/<var>index.php</var>/news/article/my_article</code>

+<code>example.com/<var>index.php</var>/news/article/my_article</code>

 

 <p>You can easily remove this file by using a .htaccess file with some simple rules. Here is an example

  of such a file, using the "negative" method in which everything is redirected except the specified items:</p>

@@ -105,11 +105,11 @@ a request for your index.php file.</p>
 <p>In your <dfn>config/config.php</dfn> file you can specify a suffix that will be added to all URLs generated

 by CodeIgniter.  For example, if a URL is this:</p>

 

-<code>www.your-site.com/index.php/products/view/shoes</code>

+<code>example.com/index.php/products/view/shoes</code>

 

 <p>You can optionally add a suffix, like <kbd>.html</kbd>, making the page appear to be of a certain type:</p>

 

-<code>www.your-site.com/index.php/products/view/shoes.html</code>

+<code>example.com/index.php/products/view/shoes.html</code>

 

 

 <h2>Enabling Query Strings</h2>

diff --git a/user_guide/general/views.html b/user_guide/general/views.html
index 3417f55b4..8ccc8d471 100644
--- a/user_guide/general/views.html
+++ b/user_guide/general/views.html
@@ -111,7 +111,7 @@ class Blog extends Controller {
 

 <p>If you visit the your site using the URL you did earlier you should see your new view.  The URL was similar to this:</p>

 

-<code>www.your-site.com/index.php/<var>blog</var>/</code>

+<code>example.com/index.php/<var>blog</var>/</code>

 

 <h2>Loading multiple views</h2>

 <p>CodeIgniter will intelligently handle  multiple calls to $this-&gt;load-&gt;view from within a controller.  If more then one call happens they will be appended together. For example, you may wish to have a header view, a menu view, a content view, and a footer view. That might look something like this:</p>