API fixes

[lrnv]

API

snake_case vs. camelCase

Functions within the package switch back and forth between using snake_case and CamelCase. It would be ideal if there could be some consistency.

https://lrnv.github.io/cort/reference/index.html

Moreover, could the reference portion of the API on the pkgdown website be split into subcategories? e.g. data/cort/copulas.

Minor note: Cort() uses N= whereas elsewhere all function parameters are lower-case.

Originally posted by @coatless in openjournals/joss-reviews#2653 (comment)

[lrnv]

Fixing the reference index, you can now see that the CamelCase and snake_case switches are to seperate constructors and standard (r/d/p/v)-functions from methods and the rest. Take a look at the new reference, you will see that the common uses of the two standards makes sense now that it's ordered.

For the last minor note : N is the number of bootstraps, and is intensionally given in uppercase as it is common in R, see e.g boot::boot, and many others.