-The data in these slots is distributed over a number of servers, using the
-same erasure coding that CHK files use, with 3-of-10 being a typical choice
-of encoding parameters. The data is encrypted and signed in such a way that
-only the holders of the read-write URI will be able to set the contents of
-the slot, and only the holders of the read-only URI will be able to read
-those contents. Holders of either URI will be able to validate the contents
-as being written by someone with the read-write URI. The servers who hold the
-shares cannot read or modify them: the worst they can do is deny service (by
-deleting or corrupting the shares), or attempt a rollback attack (which can
-only succeed with the cooperation of at least k servers).
+The data in these files is distributed over a number of servers, using the
+same erasure coding that immutable files use, with 3-of-10 being a typical
+choice of encoding parameters. The data is encrypted and signed in such a way
+that only the holders of the read-write cap will be able to set the contents
+of the slot, and only the holders of the read-only cap will be able to read
+those contents. Holders of either cap will be able to validate the contents
+as being written by someone with the read-write cap. The servers who hold the
+shares are not automatically given the ability read or modify them: the worst
+they can do is deny service (by deleting or corrupting the shares), or
+attempt a rollback attack (which can only succeed with the cooperation of at
+least k servers).
+