Merge pull request #17199 from github/8456-remove-old-references

Remove references to a deprecated data flow library for C/C++

Author: felicitymay

docs/codeql/codeql-language-guides/advanced-dataflow-scenarios-cpp.rst

@@ -1,7 +1,5 @@
 .. _advanced-dataflow-scenarios-cpp:
 
-.. include:: ../reusables/cpp-new-dataflow-api-note.rst
-
 Advanced dataflow scenarios for C/C++
 ======================================
 
@@ -102,7 +100,7 @@ This data flow is simple to match because the CodeQL database contains the infor
 Flow from a qualifier to a field access
 ---------------------------------------
 
-Sometimes field accesses are not visible to CodeQL (for example, because the implementation of the function isn't included in the database), and so dataflow cannot match up all stores with reads. This leads to missing (false negative) results. 
+Sometimes field accesses are not visible to CodeQL (for example, because the implementation of the function isn't included in the database), and so dataflow cannot match up all stores with reads. This leads to missing (false negative) results.
 
 For example, consider an alternative setup where our source of data starts as the outgoing argument of a function ``write_user_input_to``. We can model this setup in the dataflow library using the following ``isSource``:
 
@@ -456,4 +454,4 @@ The ``allowImplicitRead`` predicate specifies that if we're at a node that satis
   3. The data flowing to the indirection of ``&b`` (i.e., the object ``b``).
   4. An implicit read of the field ``x`` followed by an implicit read of the field ``a`` at the sink.
 
-Thus, we end up at a node that satisfies ``isSink`` with an empty access path, and successfully track the full dataflow path.
+Thus, we end up at a node that satisfies ``isSink`` with an empty access path, and successfully track the full dataflow path.