# HG changeset patch
# User Javier Rojas <jerojasro@devnull.li>
# Date 1224968706 18000
# Node ID 6c5ec67f47f977ccc33b5e0778f8456f04795484
# Parent  5c676825e7a173639e34d30a521bbed35a02df42
translated a couple of paragraphs of section 1.6

diff -r 5c676825e7a1 -r 6c5ec67f47f9 es/tour-basic.tex
--- a/es/tour-basic.tex	Sat Oct 25 15:52:56 2008 -0500
+++ b/es/tour-basic.tex	Sat Oct 25 16:05:06 2008 -0500
@@ -346,17 +346,18 @@
 \hggopt{--verbose}\ndt{Prolijo.}), y menos cuando se les pase la opci坦n \hggopt{-q}
 (o \hggopt{--quiet}\ndt{Silencioso.}).
 
-\section{Making and reviewing changes}
+\section{Hacer y repasar cambios}
 
-Now that we have a grasp of viewing history in Mercurial, let's take a
-look at making some changes and examining them.
+Ahora que tenemos una comprensi坦n adecuada sobre c坦mo revisar el
+historial en Mercurial, hagamos algunos cambios y veamos c坦mo
+examinarlos.
 
-The first thing we'll do is isolate our experiment in a repository of
-its own.  We use the \hgcmd{clone} command, but we don't need to
-clone a copy of the remote repository.  Since we already have a copy
-of it locally, we can just clone that instead.  This is much faster
-than cloning over the network, and cloning a local repository uses
-less disk space in most cases, too.
+Lo primero que haremos ser叩 aislar nuestro experimento en un
+repositorio propio. Usaremos el comando \hgcmd{clone}, pero no hace
+falta clonar una copia de el repositorio remoto. Como ya contamos con
+una copia local del mismo, podemos clonar esa. Esto es mucho m叩s
+r叩pido que clonar a trav辿s de la red, y en la mayor鱈a de los casos
+clonar un repositorio local usa menos espacio en disco tambi辿n.
 \interaction{tour.reclone}
 As an aside, it's often good practice to keep a ``pristine'' copy of a
 remote repository around, which you can then make temporary clones of