minor: small improvements in doc about installation

Author: mrava87

README.md

@@ -107,33 +107,37 @@ This repository is organized as follows:
 ## Getting started
 You need **Python 3.10 or greater**.
 
-#### From Conda
+#### From PyPI
+To get the most out of PyProximal straight out of the box, we recommend using
+the PyPI distribution via `uv`:
 
-To get the most out of PyLops straight out of the box, we recommend `conda` to install PyLops:
 ```bash
-conda install -c conda-forge pyproximal
+uv pip install pyproximal
 ```
 
-#### From PyPI
-You can also install pyproximal with `pip`:
+or directly via `pip`:
+
 ```bash
 pip install pyproximal
 ```
-or via `uv`:
+
+#### From Conda
+You can also install PyProximal via `conda`:
+
 ```bash
-uv pip install pyproximal
+conda install -c conda-forge pyproximal
 ```
 
 #### From Github
-Finally, you can also directly install from the main branch (although this is not recommended):
+Finally, you can also directly install from the main branch (although this is not recommended) via `uv`:
 
-```
-pip install git+https://git@github.com/PyLops/pyproximal.git@main
-```
-or via `uv`:
 ```bash
 uv add git+https://github.com/PyLops/pyproximal.git --branch main
 ```
+or via `pip`:
+```bash
+pip install git+https://git@github.com/PyLops/pyproximal.git@main
+```
 
 ## Contributing
 *Feel like contributing to the project? Adding new operators or tutorial?*
@@ -150,8 +154,8 @@ Execute the following command in your terminal:
 git clone https://github.com/your_name_here/pyproximal.git
 ```
 
-### 2. Install PyLops in a new Conda environment
-To ensure that further development of PyLops is performed within the same environment (i.e.,
+### 2. Install PyProximal in a new Conda environment
+To ensure that further development of PyProximal is performed within the same environment (i.e.,
 same dependencies) as that defined by ``environment-dev.yml``/``environment-dev-arm.yml`` files,
 we suggest to work off a new Conda enviroment.
 

docs/source/contributing.rst

@@ -113,7 +113,7 @@ will also be run as part of our CI.
 
 .. tab-set::
 
-   .. tab-item::  conda
+   .. tab-item::  :iconify:`devicon:anaconda` conda
 
         .. code-block:: bash
 

docs/source/installation.rst

@@ -37,17 +37,17 @@ First install `pyproximal` with your package manager of choice.
 
             >> conda install --channel conda-forge pyproximal
 
-        Most of the dependencies (all required and some of the optional) are
-        automatically installed for you.
+        which installs also the *required* dependencies, if not already present
+        in your environment.
 
    .. tab-item:: :iconify:`material-icon-theme:uv` uv
 
         .. code-block:: bash
 
             >> uv add pyproximal
         
-        Only the *required* dependencies are installed. To install
-        some of the optional dependencies, run:
+        which installs also the *required* dependencies, if not already present
+        in your environment. To also install the optional dependencies, run:
 
         .. code-block:: bash
 
@@ -79,7 +79,8 @@ Step-by-step installation for developers
 
 Fork PyProximal
 ===============
-Fork the `PyProximal repository <https://github.com/PyLops/pyproximal>`_ and clone it by executing the following in your terminal:
+Fork the `PyProximal repository <https://github.com/PyLops/pyproximal>`_ and clone it
+by executing the following in your terminal:
 
 .. code-block:: bash
 
@@ -175,8 +176,8 @@ At this point, the user must check the changes and then stage them before trying
 
 Final steps
 ===========
-PyProximal does not enforce the use of a linter as a pre-commit hook, but we do highly encourage using one before submitting a Pull Request.
-A properly configured linter (``ruff``) can be run with:
+PyProximal does enforce the use of a linter (``ruff``), which is run both as a pre-commit hook and as a GitHub Action.
+The linter can also be run locally with:
 
 .. tab-set::