summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-04 13:09:48 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-04 13:09:48 -0400
commit400ef405ca5aeaebcf7c22411ae3a29388986715 (patch)
tree060ccd4387521772a43a8507a60b5aaa77c4a659
parentdceea4d5f3c462a8c6806c2290936ce99acb64ee (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 f47dc7d01..c7b70468d 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 align=right>[[more about transferring data|transferring_data]]</span>
+<span float=right>[[more about transferring data|transferring_data]]</span>
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 align=right>[[more about distributed version control|distributed_version_control]]</span>
+<span float=right>[[more about distributed version control|distributed_version_control]]</span>
diff --git a/doc/use_case/Bob.mdwn b/doc/use_case/Bob.mdwn
index 8fb8e8aae..21cce21de 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 align=right>[[more about location tracking|location_tracking]]</span>
+<span float=right>[[more about location tracking|location_tracking]]</span>
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 align=right>[[more about future-proofing|future_proofing]]</span>
+<span float=right>[[more about future-proofing|future_proofing]]</span>
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 align=right>[[more about backup copies|copies]]</span>
+<span float=right>[[more about backup copies|copies]]</span>