[website] Fix wrong links

Summary: ^^

Reviewed By: thizanne

Differential Revision:
D58882818

Privacy Context Container: L1208441

fbshipit-source-id: 680af757810f5f769694785745001c1a91150d9a

infer/documentation/issues/EXECUTION_TIME_COMPLEXITY_INCREASE.md

@@ -2,6 +2,6 @@ Infer reports this issue when the execution time complexity of a
 program increases in degree: e.g. from constant to linear or from
 logarithmic to quadratic. This issue type is only reported in
 differential mode: i.e when we are comparing the cost analysis results of
-two runs of infer on a file. Check out examples in [here](/docs/next/checker-cost#examples).
+two runs of infer on a file. Check out examples in [here](/docs/next/checker-cost#examples-execution-cost).
 
 

infer/documentation/issues/PULSE_DICT_MISSING_KEY.md

@@ -1,4 +1,4 @@
-This issue is similar to [`UNINITIALIZED_VALUE` issue](#uninitialized_value), but it is to warn
+This issue is similar to [`PULSE_UNINITIALIZED_VALUE`](#pulse_uninitialized_value), but it is to warn
 reading a missing key of dictionary in Hack.
 
 For example, in the following code, the dictionary `$d` has no entry for `bye`, so reading

infer/documentation/issues/PULSE_UNINITIALIZED_CONST.md

@@ -1,4 +1,4 @@
-This issue is similar to [`UNINITIALIZED_VALUE` issue](#uninitialized_value), but it is to detect the uninitialized abstract const value in Hack.
+This issue is similar to [`PULSE_UNINITIALIZED_VALUE`](#pulse_uninitialized_value), but it is to detect the uninitialized abstract const value in Hack.
 
 For example, in the following code, the `FIELD` can be read by the static method `get_field`.
 

infer/documentation/issues/TOPL_ERROR.md

@@ -3,4 +3,4 @@ There is an execution path in the code that drives a Topl property from a start
 
 This indicates that the code has a user-defined undesired behavior.
 
-See [Topl](/docs/next/checker-topl##what-is-it) for an example
+See [Topl](/docs/next/checker-topl#what-is-it) for an example

infer/src/base/IssueType.ml

@@ -736,7 +736,7 @@ let expensive_loop_invariant_call =
 
 let memory_leak =
   register ~enabled:false ~category:ResourceLeak ~id:"BIABDUCTION_MEMORY_LEAK" ~hum:"Memory Leak"
-    Error Biabduction ~user_documentation:"See [MEMORY_LEAK](#memory_leak)."
+    Error Biabduction ~user_documentation:"See [MEMORY_LEAK_C](#memory_leak_c)."
 
 
 let missing_fld = register_hidden ~id:"Missing_fld" ~hum:"Missing Field" Error Biabduction

website/blog/2016-06-23-first-opensourceversary.md

@@ -13,7 +13,7 @@ The Infer GitHub repo has seen a lot of activity since then:
 - 339 [issues](https://github.com/facebook/infer/issues) opened
 - 44 [pull requests](https://github.com/facebook/infer/pulls) by 15 contributors
 - 10 [releases](https://github.com/facebook/infer/releases/)
-- 5 [external companies](/#who-uses-infer) officially using Infer (add yourself
+- 5 external companies officially using Infer (add yourself
   [here](https://github.com/facebook/infer/edit/main/website/src/pages/index.js))
 
 Infer was presented at 13 academic and tech international conferences, and at 8

website/docs/01-infer-workflow.md

@@ -130,7 +130,7 @@ all the compilation commands and stores the results in Infer's internal format.
 
 Next, if you change some files in your project, for instance in response to an
 Infer report, or as part of normal development, you can either clean and
-reanalyze the entire project (as in the [global workflow](#Global-workflow)
+reanalyze the entire project (as in the [global workflow](#global-workflow)
 above), or else tell Infer that you are interested in the effects of the code
 change. The second option can be significantly faster, as only a subset of the
 project needs to be analyzed: the modified files/procedures and their

website/docs/04-absint-framework.md

@@ -34,7 +34,7 @@ don't, but are feeling bold).
 Take a look at
 [liveness.ml](https://github.com/facebook/infer/blob/main/infer/src/checkers/liveness.ml).
 This code is performing a compilers-101 style liveness analysis over
-[SIL](#ir-basics-sil-cfgs-tenvs-procdescs-and-procnames), Infer's intermediate
+SIL, Infer's intermediate
 language. Since this code is fairly small and you should already understand what
 it's trying to do, it's a fairly good place to look in order to understand both
 how to use the abstract interpretation framework and what SIL is.

website/docs/all-issue-types.md

@@ -159,7 +159,7 @@ A latent [BAD_RETURN](#bad_return). See the [documentation on Pulse latent issue
 
 *Category: [Resource leak](/docs/next/all-categories#resource-leak). Reported as "Memory Leak" by [biabduction](/docs/next/checker-biabduction).*
 
-See [MEMORY_LEAK](#memory_leak).
+See [MEMORY_LEAK_C](#memory_leak_c).
 ## BIABDUCTION_RETAIN_CYCLE
 
 *Category: [Resource leak](/docs/next/all-categories#resource-leak). Reported as "Retain Cycle" by [biabduction](/docs/next/checker-biabduction).*
@@ -686,7 +686,7 @@ Infer reports this issue when the execution time complexity of a
 program increases in degree: e.g. from constant to linear or from
 logarithmic to quadratic. This issue type is only reported in
 differential mode: i.e when we are comparing the cost analysis results of
-two runs of infer on a file. Check out examples in [here](/docs/next/checker-cost#examples).
+two runs of infer on a file. Check out examples in [here](/docs/next/checker-cost#examples-execution-cost).
 
 
 
@@ -1894,7 +1894,7 @@ void const_refable(std::vector<int> vec) {
 
 *Category: [Runtime exception](/docs/next/all-categories#runtime-exception). Reported as "Dict Missing Key" by [pulse](/docs/next/checker-pulse).*
 
-This issue is similar to [`UNINITIALIZED_VALUE` issue](#uninitialized_value), but it is to warn
+This issue is similar to [`PULSE_UNINITIALIZED_VALUE`](#pulse_uninitialized_value), but it is to warn
 reading a missing key of dictionary in Hack.
 
 For example, in the following code, the dictionary `$d` has no entry for `bye`, so reading
@@ -2027,7 +2027,7 @@ Failure to `await` an `Awaitable` can lead to non-deterministic amount of the as
 
 *Category: [Runtime exception](/docs/next/all-categories#runtime-exception). Reported as "Uninitialized Const" by [pulse](/docs/next/checker-pulse).*
 
-This issue is similar to [`UNINITIALIZED_VALUE` issue](#uninitialized_value), but it is to detect the uninitialized abstract const value in Hack.
+This issue is similar to [`PULSE_UNINITIALIZED_VALUE`](#pulse_uninitialized_value), but it is to detect the uninitialized abstract const value in Hack.
 
 For example, in the following code, the `FIELD` can be read by the static method `get_field`.
 
@@ -2954,7 +2954,7 @@ There is an execution path in the code that drives a Topl property from a start
 
 This indicates that the code has a user-defined undesired behavior.
 
-See [Topl](/docs/next/checker-topl##what-is-it) for an example
+See [Topl](/docs/next/checker-topl#what-is-it) for an example
 
 ## TOPL_ERROR_LATENT
 

website/docs/support.md

@@ -108,7 +108,7 @@ for an up-to-date list of dependencies and how to get them.
 
 ### My problem is not listed here
 
-Do not hesitate to [contact us](support#need-help?).
+Do not hesitate to [contact us](#need-help).
 
 ## FAQ
 

website/src/pages/index.js

@@ -202,7 +202,7 @@ function Home() {
             </p>
           </div>
         </section>
-        <section className={styles.whoUses}>
+        <section className={styles.whoUses} id="who-uses-infer">
           <div className="container">
             <h2>Who Uses Infer?</h2>
             <div style={{ margin: "4rem 0" }}>

website/versioned_docs/version-1.1.0/01-infer-workflow.md

@@ -130,7 +130,7 @@ all the compilation commands and stores the results in Infer's internal format.
 
 Next, if you change some files in your project, for instance in response to an
 Infer report, or as part of normal development, you can either clean and
-reanalyze the entire project (as in the [global workflow](#Global-workflow)
+reanalyze the entire project (as in the [global workflow](#global-workflow)
 above), or else tell Infer that you are interested in the effects of the code
 change. The second option can be significantly faster, as only a subset of the
 project needs to be analyzed: the modified files/procedures and their

website/versioned_docs/version-1.1.0/04-absint-framework.md

@@ -34,7 +34,7 @@ don't, but are feeling bold).
 Take a look at
 [liveness.ml](https://github.com/facebook/infer/blob/main/infer/src/checkers/liveness.ml).
 This code is performing a compilers-101 style liveness analysis over
-[SIL](#ir-basics-sil-cfgs-tenvs-procdescs-and-procnames), Infer's intermediate
+SIL, Infer's intermediate
 language. Since this code is fairly small and you should already understand what
 it's trying to do, it's a fairly good place to look in order to understand both
 how to use the abstract interpretation framework and what SIL is.

website/versioned_docs/version-1.1.0/support.md

@@ -108,7 +108,7 @@ for an up-to-date list of dependencies and how to get them.
 
 ### My problem is not listed here
 
-Do not hesitate to [contact us](support#need-help?).
+Do not hesitate to [contact us](#need-help).
 
 ## FAQ
 

website/versioned_docs/version-1.2.0/01-infer-workflow.md

@@ -130,7 +130,7 @@ all the compilation commands and stores the results in Infer's internal format.
 
 Next, if you change some files in your project, for instance in response to an
 Infer report, or as part of normal development, you can either clean and
-reanalyze the entire project (as in the [global workflow](#Global-workflow)
+reanalyze the entire project (as in the [global workflow](#global-workflow)
 above), or else tell Infer that you are interested in the effects of the code
 change. The second option can be significantly faster, as only a subset of the
 project needs to be analyzed: the modified files/procedures and their

website/versioned_docs/version-1.2.0/04-absint-framework.md

@@ -34,7 +34,7 @@ don't, but are feeling bold).
 Take a look at
 [liveness.ml](https://github.com/facebook/infer/blob/main/infer/src/checkers/liveness.ml).
 This code is performing a compilers-101 style liveness analysis over
-[SIL](#ir-basics-sil-cfgs-tenvs-procdescs-and-procnames), Infer's intermediate
+SIL, Infer's intermediate
 language. Since this code is fairly small and you should already understand what
 it's trying to do, it's a fairly good place to look in order to understand both
 how to use the abstract interpretation framework and what SIL is.

website/versioned_docs/version-1.2.0/all-issue-types.md

@@ -159,7 +159,7 @@ A latent [BAD_RETURN](#bad_return). See the [documentation on Pulse latent issue
 
 *Category: [Resource leak](/docs/all-categories#resource-leak). Reported as "Memory Leak" by [biabduction](/docs/checker-biabduction).*
 
-See [MEMORY_LEAK](#memory_leak).
+See [MEMORY_LEAK_C](#memory_leak_c).
 ## BIABDUCTION_RETAIN_CYCLE
 
 *Category: [Resource leak](/docs/all-categories#resource-leak). Reported as "Retain Cycle" by [biabduction](/docs/checker-biabduction).*
@@ -686,7 +686,7 @@ Infer reports this issue when the execution time complexity of a
 program increases in degree: e.g. from constant to linear or from
 logarithmic to quadratic. This issue type is only reported in
 differential mode: i.e when we are comparing the cost analysis results of
-two runs of infer on a file. Check out examples in [here](/docs/checker-cost#examples).
+two runs of infer on a file. Check out examples in [here](/docs/checker-cost#examples-execution-cost).
 
 
 
@@ -1894,7 +1894,7 @@ void const_refable(std::vector<int> vec) {
 
 *Category: [Runtime exception](/docs/all-categories#runtime-exception). Reported as "Dict Missing Key" by [pulse](/docs/checker-pulse).*
 
-This issue is similar to [`UNINITIALIZED_VALUE` issue](#uninitialized_value), but it is to warn
+This issue is similar to [`PULSE_UNINITIALIZED_VALUE`](#pulse_uninitialized_value), but it is to warn
 reading a missing key of dictionary in Hack.
 
 For example, in the following code, the dictionary `$d` has no entry for `bye`, so reading
@@ -2027,7 +2027,7 @@ Failure to `await` an `Awaitable` can lead to non-deterministic amount of the as
 
 *Category: [Runtime exception](/docs/all-categories#runtime-exception). Reported as "Uninitialized Const" by [pulse](/docs/checker-pulse).*
 
-This issue is similar to [`UNINITIALIZED_VALUE` issue](#uninitialized_value), but it is to detect the uninitialized abstract const value in Hack.
+This issue is similar to [`PULSE_UNINITIALIZED_VALUE`](#pulse_uninitialized_value), but it is to detect the uninitialized abstract const value in Hack.
 
 For example, in the following code, the `FIELD` can be read by the static method `get_field`.
 
@@ -2954,7 +2954,7 @@ There is an execution path in the code that drives a Topl property from a start
 
 This indicates that the code has a user-defined undesired behavior.
 
-See [Topl](/docs/checker-topl##what-is-it) for an example
+See [Topl](/docs/checker-topl#what-is-it) for an example
 
 ## TOPL_ERROR_LATENT
 

website/versioned_docs/version-1.2.0/support.md

@@ -108,7 +108,7 @@ for an up-to-date list of dependencies and how to get them.
 
 ### My problem is not listed here
 
-Do not hesitate to [contact us](support#need-help?).
+Do not hesitate to [contact us](#need-help).
 
 ## FAQ