[svnbook commit] r2859 - trunk/src/en/book
cmpilato
noreply at red-bean.com
Wed Aug 15 10:38:35 CDT 2007
Author: cmpilato
Date: Wed Aug 15 10:38:34 2007
New Revision: 2859
Log:
s/schema/scheme/ when talking about URLs. Fix some other uses of 'schema' to
use more common terminology.
Modified:
trunk/src/en/book/appb-svn-for-cvs-users.xml
trunk/src/en/book/ch01-fundamental-concepts.xml
trunk/src/en/book/ch03-advanced-topics.xml
trunk/src/en/book/ch05-repository-admin.xml
trunk/src/en/book/ch06-server-configuration.xml
trunk/src/en/book/ch08-embedding-svn.xml
Modified: trunk/src/en/book/appb-svn-for-cvs-users.xml
==============================================================================
--- trunk/src/en/book/appb-svn-for-cvs-users.xml (original)
+++ trunk/src/en/book/appb-svn-for-cvs-users.xml Wed Aug 15 10:38:34 2007
@@ -511,7 +511,7 @@
<para>The exception to this behavior, however, is in the case of
accessing an <command>svnserve</command> server over an SSH
- tunnel, using the <literal>svn+ssh://</literal> URL schema. In
+ tunnel, using the <literal>svn+ssh://</literal> URL scheme. In
that case, the <command>ssh</command> program unconditionally
demands authentication just to start the tunnel.</para>
Modified: trunk/src/en/book/ch01-fundamental-concepts.xml
==============================================================================
--- trunk/src/en/book/ch01-fundamental-concepts.xml (original)
+++ trunk/src/en/book/ch01-fundamental-concepts.xml Wed Aug 15 10:38:34 2007
@@ -533,7 +533,7 @@
set things up for you. A repository location, however, is
always a URL.
<xref linkend="svn.basic.in-action.wc.tbl-1"/> describes how
- different URL schemas map to the available access
+ different URL schemes map to the available access
methods.</para>
<table id="svn.basic.in-action.wc.tbl-1">
Modified: trunk/src/en/book/ch03-advanced-topics.xml
==============================================================================
--- trunk/src/en/book/ch03-advanced-topics.xml (original)
+++ trunk/src/en/book/ch03-advanced-topics.xml Wed Aug 15 10:38:34 2007
@@ -2938,7 +2938,7 @@
repository, however, it makes a network request, and the
server responds with an appropriate answer. The details of
the network protocol are hidden from the user—the client
- attempts to access a URL, and depending on the URL schema, a
+ attempts to access a URL, and depending on the URL scheme, a
particular protocol is used to contact the server (see <xref
linkend="svn.basic.in-action.wc.sb-1"/>).</para>
Modified: trunk/src/en/book/ch05-repository-admin.xml
==============================================================================
--- trunk/src/en/book/ch05-repository-admin.xml (original)
+++ trunk/src/en/book/ch05-repository-admin.xml Wed Aug 15 10:38:34 2007
@@ -313,7 +313,7 @@
</screen>
<para>Lay out your repository in whatever way you see fit.
- Subversion does not expect or enforce a layout schema—in
+ Subversion does not expect or enforce a particular layout—in
its eyes, a directory is a directory is a directory.
Ultimately, you should choose the repository arrangement that
meets the needs of the people who work on the projects that
Modified: trunk/src/en/book/ch06-server-configuration.xml
==============================================================================
--- trunk/src/en/book/ch06-server-configuration.xml (original)
+++ trunk/src/en/book/ch06-server-configuration.xml Wed Aug 15 10:38:34 2007
@@ -432,7 +432,7 @@
custom, stateful protocol. Clients contact an
<command>svnserve</command> server by using URLs that begin with
the <literal>svn://</literal> or <literal>svn+ssh://</literal>
- schema. This section will explain the different ways of running
+ scheme. This section will explain the different ways of running
<command>svnserve</command>, how clients authenticate themselves
to the server, and how to configure appropriate access control
to your repositories.</para>
@@ -874,7 +874,7 @@
<para>It's easy to use SSH in conjunction with
<command>svnserve</command>. The client simply uses the
- <literal>svn+ssh://</literal> URL schema to connect:</para>
+ <literal>svn+ssh://</literal> URL scheme to connect:</para>
<screen>
$ whoami
@@ -965,9 +965,9 @@
</screen>
<para>And now, you can use this new tunnel definition by using a
- URL schema that matches the name of your new variable:
+ URL scheme that matches the name of your new variable:
<literal>svn+rsh://host/path</literal>. When using the new
- URL schema, the Subversion client will actually be running the
+ URL scheme, the Subversion client will actually be running the
command <command>rsh host svnserve -t</command> behind the
scenes. If you include a username in the URL (for example,
<literal>svn+rsh://username@host/path</literal>) the client
Modified: trunk/src/en/book/ch08-embedding-svn.xml
==============================================================================
--- trunk/src/en/book/ch08-embedding-svn.xml (original)
+++ trunk/src/en/book/ch08-embedding-svn.xml Wed Aug 15 10:38:34 2007
@@ -403,7 +403,7 @@
<command>svnserve</command>).</para>
<para>Since Subversion uses URLs to identify its repository
- resources, the protocol portion of the URL schema (usually
+ resources, the protocol portion of the URL scheme (usually
<literal>file://</literal>, <literal>http://</literal>,
<literal>https://</literal>, <literal>svn://</literal>, or
<literal>svn+ssh://</literal>) is used to determine which RA
More information about the svnbook-dev
mailing list