From 8f94c4c1770a62d3e824b7e27b007643271e405c Mon Sep 17 00:00:00 2001 From: Ronak Buch Date: Thu, 20 Oct 2016 16:43:35 -0500 Subject: [PATCH] Fix spelling errors in entry documentation Change-Id: I8f7e07301dca935500a27ae374cdf19d322d284c --- doc/charm++/entry.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/charm++/entry.tex b/doc/charm++/entry.tex index 935e32fa12..b3f5f23f60 100644 --- a/doc/charm++/entry.tex +++ b/doc/charm++/entry.tex @@ -62,7 +62,7 @@ performance analysis. \index{immediate}\item[immediate] entry methods are executed in an ``immediate'' fashion as they skip the message scheduling while other normal -entry methods donot. Immediate entry methods should be only associcated with +entry methods do not. Immediate entry methods should be only associated with NodeGroup objects although it is not checked during compilation. If the destination of such entry method is on the local node, then the method will be executed in the context of the regular PE regardless the execution mode of @@ -106,7 +106,7 @@ available only for Group objects and Chare Array objects. The user has to guarantee that the recipient chare element reside on the same PE. Otherwise, the application will abort on a failure. If the \kw{local} entry method uses parameter marshalling, instead of marshalling input parameters into a message, -it will pass them direcly to the callee. This implies that the callee can +it will pass them directly to the callee. This implies that the callee can modify the caller data if method parameters are passed by pointer or reference. Furthermore, input parameters do not require to be PUPable. Considering that these entry methods always execute immediately, they are allowed to have a -- 2.11.4.GIT