Update documentation

_sources/faq.rst.txt

@@ -6,20 +6,20 @@ Frequently Asked Questions
 Data Processing
 ***************
 
-Can I process two or more orthophoto GeoTIFFs to stitch them together? 
+Can I process two or more orthophoto GeoTIFFs to stitch them together?
 ----------------------------------------------------------------------
 
 No. ODM is a photogrammetric pipeline and orthophotos do not have the necessary camera information since the images have already been orthorectified. You can use another program such as `Hugin <http://hugin.sourceforge.net/>`_ to do that.
 
 The software is not using all of my CPU cores / memory / GPU all of the times. Is it normal?
----------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------
 
 Yes. The software tries to use all available resources, when possible, but not always. It's normal to see 10-15% resource utilization at several moments during processing.
 
 If I use the native version of the software, how can I allocate more resources for processing?
 ----------------------------------------------------------------------------------------------
 
-No need; the native (non-docker) version of the software alredy uses all available resources.
+No need; the native (non-docker) version of the software already uses all available resources.
 
 *********
 Licensing
@@ -43,13 +43,13 @@ Your computer is running out of memory, what can you do?
 --------------------------------------------------------
 
 1. First you can buy more RAM, this is the ultimate and final solution.
-2. Alternatively you can resize the images when uploading and/or tweak your quality settings. 
+2. Alternatively you can resize the images when uploading and/or tweak your quality settings.
 3. Configure a swapfile. In both Windows and Linux you will need preferably a fast SSD or an NVME drive, and the computing process will be still a LOT slower.
 
   - If you are using Windows with `Docker+WSL2 <https://docs.docker.com/desktop/windows/wsl/>`_ you can add two rows in your .wslconfig file so that Docker will use a swapfile. See also the full Microsoft documentation on `Advanced settings configuration in WSL <https://docs.microsoft.com/en-us/windows/wsl/wsl-config>`_.
-  
+
   .. code::
-  
+
       "swap=128GB" # you will need 128GB of disk space of course
       "swapfile=C:\\temp\\wsl-swap.vhdx" # this is where the swap file will be stored
 

es/_sources/faq.rst.txt

@@ -6,20 +6,20 @@ Frequently Asked Questions
 Data Processing
 ***************
 
-Can I process two or more orthophoto GeoTIFFs to stitch them together? 
+Can I process two or more orthophoto GeoTIFFs to stitch them together?
 ----------------------------------------------------------------------
 
 No. ODM is a photogrammetric pipeline and orthophotos do not have the necessary camera information since the images have already been orthorectified. You can use another program such as `Hugin <http://hugin.sourceforge.net/>`_ to do that.
 
 The software is not using all of my CPU cores / memory / GPU all of the times. Is it normal?
----------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------
 
 Yes. The software tries to use all available resources, when possible, but not always. It's normal to see 10-15% resource utilization at several moments during processing.
 
 If I use the native version of the software, how can I allocate more resources for processing?
 ----------------------------------------------------------------------------------------------
 
-No need; the native (non-docker) version of the software alredy uses all available resources.
+No need; the native (non-docker) version of the software already uses all available resources.
 
 *********
 Licensing
@@ -43,13 +43,13 @@ Your computer is running out of memory, what can you do?
 --------------------------------------------------------
 
 1. First you can buy more RAM, this is the ultimate and final solution.
-2. Alternatively you can resize the images when uploading and/or tweak your quality settings. 
+2. Alternatively you can resize the images when uploading and/or tweak your quality settings.
 3. Configure a swapfile. In both Windows and Linux you will need preferably a fast SSD or an NVME drive, and the computing process will be still a LOT slower.
 
   - If you are using Windows with `Docker+WSL2 <https://docs.docker.com/desktop/windows/wsl/>`_ you can add two rows in your .wslconfig file so that Docker will use a swapfile. See also the full Microsoft documentation on `Advanced settings configuration in WSL <https://docs.microsoft.com/en-us/windows/wsl/wsl-config>`_.
-  
+
   .. code::
-  
+
       "swap=128GB" # you will need 128GB of disk space of course
       "swapfile=C:\\temp\\wsl-swap.vhdx" # this is where the swap file will be stored
 

es/faq/index.html

@@ -421,7 +421,7 @@
 </section>
 <section id="if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing">
 <h3>If I use the native version of the software, how can I allocate more resources for processing?<a class="headerlink" href="#if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing" title="Enlace permanente a este encabezado"></a></h3>
-<p>No need; the native (non-docker) version of the software alredy uses all available resources.</p>
+<p>No need; the native (non-docker) version of the software already uses all available resources.</p>
 </section>
 </section>
 <section id="licensing">

faq/index.html

@@ -420,7 +420,7 @@
 </section>
 <section id="if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing">
 <h3>If I use the native version of the software, how can I allocate more resources for processing?<a class="headerlink" href="#if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing" title="Permalink to this heading"></a></h3>
-<p>No need; the native (non-docker) version of the software alredy uses all available resources.</p>
+<p>No need; the native (non-docker) version of the software already uses all available resources.</p>
 </section>
 </section>
 <section id="licensing">

fil/_sources/faq.rst.txt

@@ -6,20 +6,20 @@ Frequently Asked Questions
 Data Processing
 ***************
 
-Can I process two or more orthophoto GeoTIFFs to stitch them together? 
+Can I process two or more orthophoto GeoTIFFs to stitch them together?
 ----------------------------------------------------------------------
 
 No. ODM is a photogrammetric pipeline and orthophotos do not have the necessary camera information since the images have already been orthorectified. You can use another program such as `Hugin <http://hugin.sourceforge.net/>`_ to do that.
 
 The software is not using all of my CPU cores / memory / GPU all of the times. Is it normal?
----------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------
 
 Yes. The software tries to use all available resources, when possible, but not always. It's normal to see 10-15% resource utilization at several moments during processing.
 
 If I use the native version of the software, how can I allocate more resources for processing?
 ----------------------------------------------------------------------------------------------
 
-No need; the native (non-docker) version of the software alredy uses all available resources.
+No need; the native (non-docker) version of the software already uses all available resources.
 
 *********
 Licensing
@@ -43,13 +43,13 @@ Your computer is running out of memory, what can you do?
 --------------------------------------------------------
 
 1. First you can buy more RAM, this is the ultimate and final solution.
-2. Alternatively you can resize the images when uploading and/or tweak your quality settings. 
+2. Alternatively you can resize the images when uploading and/or tweak your quality settings.
 3. Configure a swapfile. In both Windows and Linux you will need preferably a fast SSD or an NVME drive, and the computing process will be still a LOT slower.
 
   - If you are using Windows with `Docker+WSL2 <https://docs.docker.com/desktop/windows/wsl/>`_ you can add two rows in your .wslconfig file so that Docker will use a swapfile. See also the full Microsoft documentation on `Advanced settings configuration in WSL <https://docs.microsoft.com/en-us/windows/wsl/wsl-config>`_.
-  
+
   .. code::
-  
+
       "swap=128GB" # you will need 128GB of disk space of course
       "swapfile=C:\\temp\\wsl-swap.vhdx" # this is where the swap file will be stored
 

fil/faq/index.html

@@ -420,7 +420,7 @@
 </section>
 <section id="if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing">
 <h3>If I use the native version of the software, how can I allocate more resources for processing?<a class="headerlink" href="#if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing" title="Permalink to this heading"></a></h3>
-<p>No need; the native (non-docker) version of the software alredy uses all available resources.</p>
+<p>No need; the native (non-docker) version of the software already uses all available resources.</p>
 </section>
 </section>
 <section id="licensing">

fr/_sources/faq.rst.txt

@@ -6,20 +6,20 @@ Frequently Asked Questions
 Data Processing
 ***************
 
-Can I process two or more orthophoto GeoTIFFs to stitch them together? 
+Can I process two or more orthophoto GeoTIFFs to stitch them together?
 ----------------------------------------------------------------------
 
 No. ODM is a photogrammetric pipeline and orthophotos do not have the necessary camera information since the images have already been orthorectified. You can use another program such as `Hugin <http://hugin.sourceforge.net/>`_ to do that.
 
 The software is not using all of my CPU cores / memory / GPU all of the times. Is it normal?
----------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------
 
 Yes. The software tries to use all available resources, when possible, but not always. It's normal to see 10-15% resource utilization at several moments during processing.
 
 If I use the native version of the software, how can I allocate more resources for processing?
 ----------------------------------------------------------------------------------------------
 
-No need; the native (non-docker) version of the software alredy uses all available resources.
+No need; the native (non-docker) version of the software already uses all available resources.
 
 *********
 Licensing
@@ -43,13 +43,13 @@ Your computer is running out of memory, what can you do?
 --------------------------------------------------------
 
 1. First you can buy more RAM, this is the ultimate and final solution.
-2. Alternatively you can resize the images when uploading and/or tweak your quality settings. 
+2. Alternatively you can resize the images when uploading and/or tweak your quality settings.
 3. Configure a swapfile. In both Windows and Linux you will need preferably a fast SSD or an NVME drive, and the computing process will be still a LOT slower.
 
   - If you are using Windows with `Docker+WSL2 <https://docs.docker.com/desktop/windows/wsl/>`_ you can add two rows in your .wslconfig file so that Docker will use a swapfile. See also the full Microsoft documentation on `Advanced settings configuration in WSL <https://docs.microsoft.com/en-us/windows/wsl/wsl-config>`_.
-  
+
   .. code::
-  
+
       "swap=128GB" # you will need 128GB of disk space of course
       "swapfile=C:\\temp\\wsl-swap.vhdx" # this is where the swap file will be stored
 

fr/faq/index.html

@@ -421,7 +421,7 @@
 </section>
 <section id="if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing">
 <h3>If I use the native version of the software, how can I allocate more resources for processing?<a class="headerlink" href="#if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing" title="Lien permanent vers cette rubrique"></a></h3>
-<p>No need; the native (non-docker) version of the software alredy uses all available resources.</p>
+<p>No need; the native (non-docker) version of the software already uses all available resources.</p>
 </section>
 </section>
 <section id="licensing">

id/_sources/faq.rst.txt

@@ -6,20 +6,20 @@ Frequently Asked Questions
 Data Processing
 ***************
 
-Can I process two or more orthophoto GeoTIFFs to stitch them together? 
+Can I process two or more orthophoto GeoTIFFs to stitch them together?
 ----------------------------------------------------------------------
 
 No. ODM is a photogrammetric pipeline and orthophotos do not have the necessary camera information since the images have already been orthorectified. You can use another program such as `Hugin <http://hugin.sourceforge.net/>`_ to do that.
 
 The software is not using all of my CPU cores / memory / GPU all of the times. Is it normal?
----------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------
 
 Yes. The software tries to use all available resources, when possible, but not always. It's normal to see 10-15% resource utilization at several moments during processing.
 
 If I use the native version of the software, how can I allocate more resources for processing?
 ----------------------------------------------------------------------------------------------
 
-No need; the native (non-docker) version of the software alredy uses all available resources.
+No need; the native (non-docker) version of the software already uses all available resources.
 
 *********
 Licensing
@@ -43,13 +43,13 @@ Your computer is running out of memory, what can you do?
 --------------------------------------------------------
 
 1. First you can buy more RAM, this is the ultimate and final solution.
-2. Alternatively you can resize the images when uploading and/or tweak your quality settings. 
+2. Alternatively you can resize the images when uploading and/or tweak your quality settings.
 3. Configure a swapfile. In both Windows and Linux you will need preferably a fast SSD or an NVME drive, and the computing process will be still a LOT slower.
 
   - If you are using Windows with `Docker+WSL2 <https://docs.docker.com/desktop/windows/wsl/>`_ you can add two rows in your .wslconfig file so that Docker will use a swapfile. See also the full Microsoft documentation on `Advanced settings configuration in WSL <https://docs.microsoft.com/en-us/windows/wsl/wsl-config>`_.
-  
+
   .. code::
-  
+
       "swap=128GB" # you will need 128GB of disk space of course
       "swapfile=C:\\temp\\wsl-swap.vhdx" # this is where the swap file will be stored
 

id/faq/index.html

@@ -421,7 +421,7 @@
 </section>
 <section id="if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing">
 <h3>If I use the native version of the software, how can I allocate more resources for processing?<a class="headerlink" href="#if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing" title="Permalink to this heading"></a></h3>
-<p>No need; the native (non-docker) version of the software alredy uses all available resources.</p>
+<p>No need; the native (non-docker) version of the software already uses all available resources.</p>
 </section>
 </section>
 <section id="licensing">

sw/_sources/faq.rst.txt

@@ -6,20 +6,20 @@ Frequently Asked Questions
 Data Processing
 ***************
 
-Can I process two or more orthophoto GeoTIFFs to stitch them together? 
+Can I process two or more orthophoto GeoTIFFs to stitch them together?
 ----------------------------------------------------------------------
 
 No. ODM is a photogrammetric pipeline and orthophotos do not have the necessary camera information since the images have already been orthorectified. You can use another program such as `Hugin <http://hugin.sourceforge.net/>`_ to do that.
 
 The software is not using all of my CPU cores / memory / GPU all of the times. Is it normal?
----------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------
 
 Yes. The software tries to use all available resources, when possible, but not always. It's normal to see 10-15% resource utilization at several moments during processing.
 
 If I use the native version of the software, how can I allocate more resources for processing?
 ----------------------------------------------------------------------------------------------
 
-No need; the native (non-docker) version of the software alredy uses all available resources.
+No need; the native (non-docker) version of the software already uses all available resources.
 
 *********
 Licensing
@@ -43,13 +43,13 @@ Your computer is running out of memory, what can you do?
 --------------------------------------------------------
 
 1. First you can buy more RAM, this is the ultimate and final solution.
-2. Alternatively you can resize the images when uploading and/or tweak your quality settings. 
+2. Alternatively you can resize the images when uploading and/or tweak your quality settings.
 3. Configure a swapfile. In both Windows and Linux you will need preferably a fast SSD or an NVME drive, and the computing process will be still a LOT slower.
 
   - If you are using Windows with `Docker+WSL2 <https://docs.docker.com/desktop/windows/wsl/>`_ you can add two rows in your .wslconfig file so that Docker will use a swapfile. See also the full Microsoft documentation on `Advanced settings configuration in WSL <https://docs.microsoft.com/en-us/windows/wsl/wsl-config>`_.
-  
+
   .. code::
-  
+
       "swap=128GB" # you will need 128GB of disk space of course
       "swapfile=C:\\temp\\wsl-swap.vhdx" # this is where the swap file will be stored
 

sw/faq/index.html

@@ -420,7 +420,7 @@
 </section>
 <section id="if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing">
 <h3>If I use the native version of the software, how can I allocate more resources for processing?<a class="headerlink" href="#if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing" title="Permalink to this heading"></a></h3>
-<p>No need; the native (non-docker) version of the software alredy uses all available resources.</p>
+<p>No need; the native (non-docker) version of the software already uses all available resources.</p>
 </section>
 </section>
 <section id="licensing">

te/_sources/faq.rst.txt

@@ -6,20 +6,20 @@ Frequently Asked Questions
 Data Processing
 ***************
 
-Can I process two or more orthophoto GeoTIFFs to stitch them together? 
+Can I process two or more orthophoto GeoTIFFs to stitch them together?
 ----------------------------------------------------------------------
 
 No. ODM is a photogrammetric pipeline and orthophotos do not have the necessary camera information since the images have already been orthorectified. You can use another program such as `Hugin <http://hugin.sourceforge.net/>`_ to do that.
 
 The software is not using all of my CPU cores / memory / GPU all of the times. Is it normal?
----------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------
 
 Yes. The software tries to use all available resources, when possible, but not always. It's normal to see 10-15% resource utilization at several moments during processing.
 
 If I use the native version of the software, how can I allocate more resources for processing?
 ----------------------------------------------------------------------------------------------
 
-No need; the native (non-docker) version of the software alredy uses all available resources.
+No need; the native (non-docker) version of the software already uses all available resources.
 
 *********
 Licensing
@@ -43,13 +43,13 @@ Your computer is running out of memory, what can you do?
 --------------------------------------------------------
 
 1. First you can buy more RAM, this is the ultimate and final solution.
-2. Alternatively you can resize the images when uploading and/or tweak your quality settings. 
+2. Alternatively you can resize the images when uploading and/or tweak your quality settings.
 3. Configure a swapfile. In both Windows and Linux you will need preferably a fast SSD or an NVME drive, and the computing process will be still a LOT slower.
 
   - If you are using Windows with `Docker+WSL2 <https://docs.docker.com/desktop/windows/wsl/>`_ you can add two rows in your .wslconfig file so that Docker will use a swapfile. See also the full Microsoft documentation on `Advanced settings configuration in WSL <https://docs.microsoft.com/en-us/windows/wsl/wsl-config>`_.
-  
+
   .. code::
-  
+
       "swap=128GB" # you will need 128GB of disk space of course
       "swapfile=C:\\temp\\wsl-swap.vhdx" # this is where the swap file will be stored
 

te/faq/index.html

@@ -421,7 +421,7 @@
 </section>
 <section id="if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing">
 <h3>If I use the native version of the software, how can I allocate more resources for processing?<a class="headerlink" href="#if-i-use-the-native-version-of-the-software-how-can-i-allocate-more-resources-for-processing" title="Permalink to this heading"></a></h3>
-<p>No need; the native (non-docker) version of the software alredy uses all available resources.</p>
+<p>No need; the native (non-docker) version of the software already uses all available resources.</p>
 </section>
 </section>
 <section id="licensing">