Author: Kazu Hirata Date: 2023-08-11T21:44:33-07:00 New Revision: c053345b059bd3fa7f0e5f51498c71095b7a1d88
URL: https://github.com/llvm/llvm-project/commit/c053345b059bd3fa7f0e5f51498c71095b7a1d88 DIFF: https://github.com/llvm/llvm-project/commit/c053345b059bd3fa7f0e5f51498c71095b7a1d88.diff LOG: [clang] Fix typos in documentation Added: Modified: clang/docs/analyzer/checkers.rst Removed: ################################################################################ diff --git a/clang/docs/analyzer/checkers.rst b/clang/docs/analyzer/checkers.rst index d3a4ebcaf02025..b7860af80c200d 100644 --- a/clang/docs/analyzer/checkers.rst +++ b/clang/docs/analyzer/checkers.rst @@ -2375,8 +2375,8 @@ The malicious data is injected at the taint source (e.g. ``getenv()`` call) which is then propagated through function calls and being used as arguments of sensitive operations, also called as taint sinks (e.g. ``system()`` call). -One can defend agains this type of vulnerability by always checking and -santizing the potentially malicious, untrusted user input. +One can defend against this type of vulnerability by always checking and +sanitizing the potentially malicious, untrusted user input. The goal of the checker is to discover and show to the user these potential taint source-sink pairs and the propagation call chain. @@ -2438,7 +2438,7 @@ Unfortunately, the checker cannot discover automatically that the programmer have performed data sanitation, so it still emits the warning. One can get rid of this superflous warning by telling by specifying the -sanitation functions in the taint configuation file (see +sanitation functions in the taint configuration file (see :doc:`user-docs/TaintAnalysisConfiguration`). .. code-block:: YAML _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
