update faq's answer

Author: ssurbhi560

src/user/faq.rst

@@ -81,19 +81,18 @@ FAQ
 
   If you need to compile CUDA code, even if it involves only CUDA host APIs, you will still need a valid CUDA Toolkit installed locally and use it. Please refer to `NVCC's documentation <https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html>`_ for the CUDA compiler usage and `CUDA Programming Guide <https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html>`_ for general CUDA programming.
 
-.. _faq_api_abi_breakage:
+.. _faq_abi_incompatibility:
 
-:ref:`(Q) <faq_api_abi_breakage>` **How to handle breaking of a package due to ABI/API incompatibility?**
+:ref:`(Q) <faq_abi_incompatibility>` **How to handle breaking of a package due to ABI incompatibility?**
 
-  If your package breaks due to ABI/API incompatibility, here are a few steps you can take to fix it:
+  If your package breaks ABI with a version bump, here are a few steps you can take to fix it:
 
   - Rebuild the package with corrected ``run_exports``.
-  - Hot-fix repodata of previous package to apply the right ``run_exports``.
   - Hot-fix the repodata of dependencies to include corrected pinnings for the package.
 
   To read more on how to specify ``run_exports``, see `this <https://conda-forge.org/docs/maintainer/pinning_deps.html?highlight=run_exports#specifying-run-exports>`_.
   Some of the examples you can see for reference, where broken packages are fixed by:
 
   - `Replacing an existing pin that was incorrect <https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/217>`_.
-  - `Pinning packages loosely to rely on their ABI compatibility. <https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/132>`_.
+  - `Pinning packages loosely to rely on their ABI compatibility <https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/132>`_.
   - `Pinning packages strictly <https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/154>`_.