Don't refer to user memory access as "copying". Some of the students

[pintos-anon] / doc / userprog.tmpl

diff --git a/doc/userprog.tmpl b/doc/userprog.tmpl
index 07183dbefbacd4d2aae0a76842605510af06ea6a..a8b4269e9c5c1de6025b289a91afd490c3ea3cbd 100644 (file)
--- a/doc/userprog.tmpl
+++ b/doc/userprog.tmpl
@@ -59,8 +59,7 @@ FirstName LastName <email@domain.example>
 
 ---- ALGORITHMS ----
 
->> Describe your code for copying data from user programs into the kernel
->> and vice versa.
+>> Describe your code for reading and writing user data from the kernel.
 
 >> Suppose a system call causes a full page (4,096 bytes) of data to be
 >> copied from user space into the kernel.  What is the least and the
@@ -100,8 +99,8 @@ FirstName LastName <email@domain.example>
 
 ---- RATIONALE ----
 
->> Why did you choose to implement user-to-kernel copying the way you
->> did?
+>> Why did you choose to implement access to user memory from the
+>> kernel in the way that you did?
 
 >> What advantages or disadvantages can you see to your design for file
 >> descriptors?