* At the top level, the c_first_hf list has a list of all message
* headers. If the content-type is multipart (c_type == CT_MULTIPART)
* then c_ctparams will contain a pointer to a struct multipart.
- * A struct multipart contains (among other trhings) a linked list
+ * A struct multipart contains (among other things) a linked list
* of struct part elements, and THOSE contain a pointer to the sub-part's
* Content structure.
*/
* relatively self-explanatory.
*
* If we are using SSL for encryption, then use a buffering BIO for output
- * (that just easier). Still do buffering for reads; when we need more
+ * (that's just easier). Still do buffering for reads; when we need more
* data we call the BIO_read() function to fill our local buffer.
*
* For SASL, we make use of (for now) the Cyrus-SASL library. For some
/*
* Some explanation:
*
- * startoffset is the offset from the beginning of the input buffer
- * of data that has is in our input buffer, but has not yet been
- * consumed. This can be non-zero, if, functions like netsec_readline()
- * leave leftover data.
+ * startoffset is the offset from the beginning of the input
+ * buffer to data that is in our input buffer, but has not yet
+ * been consumed. This can be non-zero if functions like
+ * netsec_readline() leave leftover data.
*
* remaining is the remaining amount of unconsumed data in the input
* buffer.