Rewording some of this documentation to describe the check instead of try to rationalize the behavior of the check. The links already provide sufficient rationale.

llvm-svn: 252496

clang-tools-extra/docs/clang-tidy/checks/cert-setlongjmp.rst

@@ -1,10 +1,7 @@
 cert-err52-cpp
 ==============
 
-The C standard library facilities setjmp() and longjmp() can be used to
-simulate throwing and catching exceptions. However, these facilities bypass
-automatic resource management and can result in undefined behavior, commonly
-including resource leaks, and denial-of-service attacks.
+This check flags all call expressions involving setjmp() and longjmp().
 
 This check corresponds to the CERT C++ Coding Standard rule
 `ERR52-CPP. Do not use setjmp() or longjmp()

clang-tools-extra/docs/clang-tidy/checks/cert-variadic-function-def.rst

@@ -1,12 +1,8 @@
 cert-dcl50-cpp
 ========================
 
-A variadic function using an ellipsis has no mechanisms to check the type safety
-of arguments being passed to the function or to check that the number of
-arguments being passed matches the semantics of the function definition.
-Consequently, a runtime call to a C-style variadic function that passes
-inappropriate arguments yields undefined behavior. Such undefined behavior could
-be exploited to run arbitrary code.
+This check flags all function definitions (but not declarations) of C-style
+variadic functions.
 
 This check corresponds to the CERT C++ Coding Standard rule
 `DCL50-CPP. Do not define a C-style variadic function