chore: lowercase for filenames

docs/user/explanation/fhe_and_framework_limits.md

@@ -10,7 +10,7 @@ However, one still has to consider that FHE is slow, as compared to the vanilla
 
 ### Multiplying by constants
 
-In the scheme used in the **Concrete Framework**, namely [TFHE](https://tfhe.github.io/tfhe/), multiplications by constants is only defined for integer constants. Notably, one can't multiply by floats. As float multiplication is very usual in the data science (think of weights of dense layers, for example), this could be a problem, but quantization is at our rescue. See [this](QUANTIZATION.md) section for more details.
+In the scheme used in the **Concrete Framework**, namely [TFHE](https://tfhe.github.io/tfhe/), multiplications by constants is only defined for integer constants. Notably, one can't multiply by floats. As float multiplication is very usual in the data science (think of weights of dense layers, for example), this could be a problem, but quantization is at our rescue. See [this](quantization.md) section for more details.
 
 ### Achieving computations of not-linear functions
 
@@ -26,7 +26,7 @@ Since this is an early version of the product, not everything is done, to say th
 FIXME(Benoit): we'll see later if this is still a valid limit, #1111
 ```
 
-As of today, the execution of the FHE program is done locally. Notably, in the current version, there is no client (on which we encrypt the private data, or decrypt the returned result) or server (on which the computation is done completely over encrypted data), but a single host. As explained in [this section](FUTURE_FEATURES.md), this limit will be removed in the next version, such that the **Concrete Framework** can be used in production.
+As of today, the execution of the FHE program is done locally. Notably, in the current version, there is no client (on which we encrypt the private data, or decrypt the returned result) or server (on which the computation is done completely over encrypted data), but a single host. As explained in [this section](future_features.md), this limit will be removed in the next version, such that the **Concrete Framework** can be used in production.
 
 ### Currently slow
 

docs/user/explanation/future_features.md

@@ -1,6 +1,6 @@
 # Future Features
 
-As explained in [this section](FHE_AND_FRAMEWORK_LIMITS.md#concrete-framework-limits), the **Concrete Framework**
+As explained in [this section](fhe_and_framework_limits.md#concrete-framework-limits), the **Concrete Framework**
 is currently in a preliminary version, and quite constrained in term of functionalities. However, the good
 news is that we are going to release new versions regularly, where a lot of functionalities will be added progressively.
 

docs/user/explanation/index.rst

@@ -4,7 +4,7 @@ Explanations
 .. toctree::
    :maxdepth: 1
 
-   WHAT_IS_FHE.md
-   FHE_AND_FRAMEWORK_LIMITS.md
-   QUANTIZATION.md
-   FUTURE_FEATURES.md
+   what_is_fhe.md
+   fhe_and_framework_limits.md
+   quantization.md
+   future_features.md

docs/user/explanation/quantization.md

@@ -1,5 +1,5 @@
 ```{warning}
-FIXME(Jordan/Andrei): see if this is still appropriate, update etc; make link with USE_QUANTIZATION.md
+FIXME(Jordan/Andrei): see if this is still appropriate, update etc; make link with use_quantization.md
 ```
 
 # Quantization
@@ -12,7 +12,7 @@ from [Wikipedia](https://en.wikipedia.org/wiki/Quantization):
 
 ## Why is it needed?
 
-Modern computing has long been using data types that use 32 or 64 bits (be that integers or floating point numbers), or even bigger data types. However due to the costly nature of FHE computations (see [the limits of FHE](FHE_AND_FRAMEWORK_LIMITS.md)), using such types with FHE is impractical (or plain impossible) to have computations executing in a reasonable amount of time.
+Modern computing has long been using data types that use 32 or 64 bits (be that integers or floating point numbers), or even bigger data types. However due to the costly nature of FHE computations (see [the limits of FHE](fhe_and_framework_limits.md)), using such types with FHE is impractical (or plain impossible) to have computations executing in a reasonable amount of time.
 
 ## The gist of quantization