Commits

Patrick Samson committed 480e631

typos

  • Participants
  • Parent commits e5962fd

Comments (0)

Files changed (6)

File Features.wiki

     </a>
 }}}
 
-=== Min/Max recipients ===
+=== Recipients Min/Max ===
 
 If you need to constraint the maximum number of recipients in the forms, you can pass the optional
 {{{max}}} parameter to the view.
 To forbid the exchange, use one of these means:
 
 * return {{{False}}} or {{{''}}}, if you do not want to give a reason for the refusal.
-  The error message will be: "Exchanging with some users is not possible: foo, bar."
+  The error message will be: "Writing to some users is not possible: foo, bar."
 
 * return a string, as a reason for the refusal.
-  The error message will be: "Exchanging with some users is not possible: foo (reason), bar (reason)."
+  The error message will be: "Writing to some users is not possible: foo (reason), bar (reason)."
 
 * raise a {{{ValidationError}}} with an error message to your liking.
 
 * by **message**, for an expanded view: each message is considered on its own.
 
 Here is a summary of features:
-* A non-User (email is unveiled) can write to a User and get a reply
+* A non-User (email is undisclosed) can write to a User and get a reply
   (can be disabled by configuration)
 * Exchanges can be moderated (with auto-accept and auto-reject plug-ins)
 * Optional recipient filter plug-ins

File Moderation.wiki

 {{{rating}}} may take the following values:
 
 * {{{None}}}
-* {{{True}}}, interpreted as 100
-* {{{False}}}, interpreted as 0
-* an integer between 0 and 100
+* 0 or {{{False}}}
+* 100 or {{{True}}}
+* an integer between 1 and 99
 
 {{{reason}}} is a string, giving a specific reason for a rejection.
 If not provided, a default reason will be taken from the attribute {{{default_reason}}} of the function,

File Quick_Start_Guide.wiki

 
 {{{urls.py}}}:
 {{{
-    url(r'^messages/', include('postman.urls')),
+    (r'^messages/', include('postman.urls')),
 }}}
 
 ----

File Tags_and_Filters.wiki

 }}}
 and the sender is the currently logged-in user, the output is compacted to show only the simple pattern '<me>'.
 
-Note that this pattern can not be confused with the username of a real user, as the brackets are not in the valid character set
+Note that this pattern cannot be confused with the username of a real user, as the brackets are not in the valid character set
 for a username.
 
 ==== compact_date ====
 The default algorithm is:
 
 # Return where you came from
-# If it can not be known, fall back to the inbox view
+# If it cannot be known, fall back to the inbox view
 # But if the submission view has a {{{success_url}}} parameter, use it preferably
 # In all cases, a {{{next}}} parameter in the query string has higher precedence