Correct capitalization of FAISS to Faiss

.github/actions/build_conda/action.yml

@@ -1,5 +1,5 @@
 name: Conda build
-description: Builds FAISS inside a Conda environment and uploads to repository when label is provided.
+description: Builds Faiss inside a Conda environment and uploads to repository when label is provided.
 inputs:
   label:
     description: "The label to be used for uploads to Conda."

INSTALL.md

@@ -109,7 +109,7 @@ section of the wiki](https://github.com/facebookresearch/faiss/wiki/Troubleshoot
 
 ### Building with NVIDIA cuVS
 
-[cuVS](https://docs.rapids.ai/api/cuvs/nightly/) contains state-of-the-art implementations of several algorithms for running approximate nearest neighbors and clustering on the GPU. It is built on top of the [RAPIDS RAFT](https://github.com/rapidsai/raft) library of high performance machine learning primitives. Building FAISS with cuVS enabled allows a user to choose between regular GPU implementations in FAISS and cuVS implementations for specific algorithms.
+[cuVS](https://docs.rapids.ai/api/cuvs/nightly/) contains state-of-the-art implementations of several algorithms for running approximate nearest neighbors and clustering on the GPU. It is built on top of the [RAPIDS RAFT](https://github.com/rapidsai/raft) library of high performance machine learning primitives. Building Faiss with cuVS enabled allows a user to choose between regular GPU implementations in Faiss and cuVS implementations for specific algorithms.
 
 The libcuvs dependency should be installed via conda:
 1. With CUDA 12.0 - 12.5:

benchs/README.md

@@ -339,7 +339,7 @@ search...
 
 # Additional benchmarks
 
-This directory also contains certain additional benchmarks (and serve as an additional source of examples of how to use the FAISS code).
+This directory also contains certain additional benchmarks (and serve as an additional source of examples of how to use the Faiss code).
 Certain tests / benchmarks might be outdated.
 
 * bench_6bit_codec.cpp - tests vector codecs for SQ6 quantization on a synthetic dataset

demos/demo_auto_tune.py

@@ -102,7 +102,7 @@ def plot_OperatingPoints(ops, nq, **kwargs):
 if use_gpu:
     # if this fails, it means that the GPU version was not comp
     assert faiss.StandardGpuResources, \
-        "FAISS was not compiled with GPU support, or loading _swigfaiss_gpu.so failed"
+        "Faiss was not compiled with GPU support, or loading _swigfaiss_gpu.so failed"
     res = faiss.StandardGpuResources()
     dev_no = 0
 

faiss/gpu/StandardGpuResources.h

@@ -162,7 +162,7 @@ class StandardGpuResourcesImpl : public GpuResources {
     /**
      * FIXME: Integrating these in a separate code path for now. Ultimately,
      * it would be nice if we use a simple memory resource abstraction
-     * in FAISS so we could plug in whether to use RMM's memory resources
+     * in Faiss so we could plug in whether to use RMM's memory resources
      * or the default.
      *
      * There's enough duplicated logic that it doesn't *seem* to make sense

faiss/utils/hamming_distance/avx512-inl.h

@@ -11,7 +11,7 @@
 // AVX512 version
 // The _mm512_popcnt_epi64 intrinsic is used to accelerate Hamming distance
 // calculations in HammingComputerDefault and HammingComputer64. This intrinsic
-// is not available in the default FAISS avx512 build mode but is only
+// is not available in the default Faiss avx512 build mode but is only
 // available in the avx512_spr build mode, which targets Intel(R) Sapphire
 // Rapids.
 

faiss/utils/utils.h

@@ -37,7 +37,7 @@ std::string get_compile_options();
  * Get some stats about the system
  **************************************************/
 
-// Expose FAISS version as a string
+// Expose Faiss version as a string
 std::string get_version();
 
 /// ms elapsed since some arbitrary epoch