Renamed all type names to CamelCaseNames for visual distinctness, separate from variables/functions

1 files changed, 2 insertions, 2 deletions

diff --git a/termkey_waitkey.3.sh b/termkey_waitkey.3.sh
index 7dda316..8a2a072 100644
--- a/termkey_waitkey.3.sh
+++ b/termkey_waitkey.3.sh
@@ -7,14 +7,14 @@ termkey_waitkey \- wait for and retrieve the next key event
 .nf
 .B #include <termkey.h>
 .sp
-.BI "termkey_result termkey_waitkey(termkey_t *" tk ", termkey_key *" key );
+.BI "TermKeyResult termkey_waitkey(TermKey *" tk ", TermKeyKey *" key );
 .fi
 .sp
 Link with \fI-ltermkey\fP.
 .SH DESCRIPTION
 \fBtermkey_waitkey\fP attempts to retrieve a single keypress event from the buffer, and put it in the structure referred to by \fIkey\fP. If successful it will return \fBTERMKEY_RES_KEY\fP to indicate that the structure now contains a new keypress event. If nothing is in the buffer it will block until one is available. If no events are ready and the input stream is now closed, will return \fBTERMKEY_RES_EOF\fP.
 .PP
-For details of the \fBtermkey_key\fP structure, see \fBtermkey_getkey\fP(3).
+For details of the \fBTermKeyKey\fP structure, see \fBtermkey_getkey\fP(3).
 .PP
 Some keypresses generate multiple bytes from the terminal. Because there may be network or other delays between the terminal and an application using termkey, \fBtermkey_waitkey\fP() will attempt to wait for the remaining bytes to arrive if it detects the start of a multibyte sequence. If no more bytes arrive within a certain time, then the bytes will be reported as they stand, even if this results in interpreting a partially-complete Escape sequence as a literal Escape key followed by some normal letters or other symbols. The amount of time to wait can be set by \fBtermkey_set_waittime\fP(3).
 .SH "RETURN VALUE"