[gnuastro-commits] master f1878bf 1/4: Minor edits and corrections book text

[Mohammad Akhlaghi]

branch: master
commit f1878bf175017a3d8f239fe09e72185d4496aae7
Author: Mohammad Akhlaghi <address@hidden>
Commit: Mohammad Akhlaghi <address@hidden>

    Minor edits and corrections book text
    
    Some minor edits were made to correct some typos and make the text
    introducing arrays of `gal_data_t' more clear.
    
    Also, while looking in MakeProfile's Info manual, I noticed that the list
    containing the different profile values (for the profile column), had two
    points before the last (radial) profile. So a space was added to between
    each item and this problem is now solved.
---
 doc/gnuastro.texi | 29 ++++++++++++++++++-----------
 1 file changed, 18 insertions(+), 11 deletions(-)

diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index 68e647e..03eb629 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -16713,19 +16713,25 @@ format}.
 @itemize
 @item
 S@'ersic profile with address@hidden' or address@hidden'.
+
 @item
 Moffat profile with address@hidden' or address@hidden'.
+
 @item
 Gaussian profile with address@hidden' or address@hidden'.
+
 @item
 Point source with address@hidden' or address@hidden'.
+
 @item
 Flat profile with address@hidden' or address@hidden'.
+
 @item
 Circumference profile with address@hidden' or address@hidden'. A fixed
 value will be used for all pixels between the truncation radius
 (@mymath{r_t}) and @mymath{r_t-w} (@mymath{w} is the value to the
 @option{--circumwidth}).
+
 @item
 Radial distance profile with address@hidden' or address@hidden'. At the lowest
 level, each pixel only has an elliptical radial distance given the
@@ -19768,12 +19774,13 @@ freed after you are done with it.
 Astronomical datasets have various dimensions, for example 1D spectra or
 table columns, 2D images, or 3D Integral field data cubes. Datasets can
 also have various numeric data types, depending on the operation/purpose,
-for example processed images are in commonly in floating point, but their
-mask images are integers using bit-wise flags to identify certain classes
-of special pixels, see @ref{Numeric data types}). Certain other information
-about a dataset are also commonly necessary, for example the units of the
-dataset, the name of the dataset and some comments. To deal with any
-generic dataset, Gnuastro defines the @code{gal_data_t} as input or output.
+for example processed images are commonly stored in floating point format,
+but their mask images are integers (allowing bit-wise flags to identify
+certain classes of pixels to keep or mask, see @ref{Numeric data
+types}). Certain other information about a dataset are also commonly
+necessary, for example the units of the dataset, the name of the dataset
+and some comments. To deal with any generic dataset, Gnuastro defines the
address@hidden as input or output.
 
 @menu
 * Generic data container::      Definition of Gnuastro's generic container.
@@ -20157,11 +20164,11 @@ simplify the allocation (and later cleaning) of 
several @code{gal_data_t}s
 that are related.
 
 For example, each column in a table is usually represented by one
address@hidden (so it has its own name, numeric data type, units and
-etc). A table (with many columns) can be seen as an array of
address@hidden (when the number of columns is known a-priori). The
-functions below are defined to create a cleared array of data structures
-and to free them in the end. These functions are declared in
address@hidden (so it has its own name, data type, units and etc). A
+table (with many columns) can be seen as an array of @code{gal_data_t}s
+(when the number of columns is known a-priori). The functions below are
+defined to create a cleared array of data structures and to free them when
+none are necessary any more. These functions are declared in
 @file{gnuastro/data.h} which is also visible from the function names (see
 @ref{Gnuastro library}).