summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-04 13:12:48 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-04 13:12:48 -0400
commit6072399dc225e4ca333fe3d424b587d151b24065 (patch)
treee371313e89e3d7c22138d9d8ea013380825accdb
parent400ef405ca5aeaebcf7c22411ae3a29388986715 (diff)
format
-rw-r--r--doc/use_case/Alice.mdwn4
-rw-r--r--doc/use_case/Bob.mdwn6
2 files changed, 5 insertions, 5 deletions
diff --git a/doc/use_case/Alice.mdwn b/doc/use_case/Alice.mdwn
index c7b70468d..4e07e2281 100644
--- a/doc/use_case/Alice.mdwn
+++ b/doc/use_case/Alice.mdwn
@@ -11,10 +11,10 @@ server for later. At a coffee shop, she has git-annex download them to her
USB drive. High in the sky or in a remote cabin, she catches up on
podcasts, videos, and games, first letting git-annex copy them from
her USB drive to the netbook (this saves battery power).
-<span float=right>[[more about transferring data|transferring_data]]</span>
+<small>[[more about transferring data|transferring_data]]</small>
When she's done, she tells git-annex which to keep and which to remove.
They're all removed from her netbook to save space, and Alice knows
that next time she syncs up to the net, her changes will be synced back
to her server.
-<span float=right>[[more about distributed version control|distributed_version_control]]</span>
+<small>[[more about distributed version control|distributed_version_control]]</small>
diff --git a/doc/use_case/Bob.mdwn b/doc/use_case/Bob.mdwn
index 21cce21de..915fa1e0b 100644
--- a/doc/use_case/Bob.mdwn
+++ b/doc/use_case/Bob.mdwn
@@ -11,15 +11,15 @@ without worry about accidentally deleting anything.
When Bob needs access to some files, git-annex can tell him which drive(s)
they're on, and easily make them available. Indeed, every drive knows what
is on every other drive.
-<span float=right>[[more about location tracking|location_tracking]]</span>
+<small>[[more about location tracking|location_tracking]]</small>
Bob thinks long-term, and so he's glad that git-annex uses a simple
repository format. He knows his files will be accessible in the future
even if the world has forgotten about git-annex and git.
-<span float=right>[[more about future-proofing|future_proofing]]</span>
+<small>[[more about future-proofing|future_proofing]]</small>
Run in a cron job, git-annex adds new files to archival drives at night. It
also helps Bob keep track of intentional, and unintentional copies of
files, and logs information he can use to decide when it's time to duplicate
the content of old drives.
-<span float=right>[[more about backup copies|copies]]</span>
+<small>[[more about backup copies|copies]]</small>