[gnuastro-commits] master dad9380: Book: typo corrected in new Memory management section

[Mohammad Akhlaghi]

branch: master
commit dad9380992e289a1e5eb50d762dd777843c1acb3
Author: Mohammad Akhlaghi <mohammad@akhlaghi.org>
Commit: Mohammad Akhlaghi <mohammad@akhlaghi.org>

    Book: typo corrected in new Memory management section
    
    Alberto Madrigal found this typo, it has been fixed with this commit.
---
 doc/gnuastro.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index bfce4e5..4b54a86 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -7654,7 +7654,7 @@ If you are writing your own program, you can use the 
@code{gal_data_copy_to_new_
 @cindex Non-volatile memory
 @cindex Memory, non-volatile
 In this section we'll review how Gnuastro manages your input data in your 
system's memory.
-Knowing this can help you optimize your usage (in speed and memory 
consumption) when the data volume ls large and approaches, or exceeds, your 
available RAM (usually in various calls to multiple programs simultaneously).
+Knowing this can help you optimize your usage (in speed and memory 
consumption) when the data volume is large and approaches, or exceeds, your 
available RAM (usually in various calls to multiple programs simultaneously).
 But before diving into the details, let's have a short basic introduction to 
memory in general and in particular the types of memory most relevant to this 
discussion.
 
 Input datasets (that are later fed into programs for analysis) are commonly 
first stored in @emph{non-volatile memory}.