gnuastro-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnuastro-commits] master 4a0f674: Trivial typos: READMEs, gnuastro.texi


From: Mohammad Akhlaghi
Subject: [gnuastro-commits] master 4a0f674: Trivial typos: READMEs, gnuastro.texi
Date: Sat, 24 Dec 2016 23:08:38 +0000 (UTC)

branch: master
commit 4a0f67422f49c74ee4223f443fa4464576c3640f
Author: Boud Roukema <address@hidden>
Commit: Mohammad Akhlaghi <address@hidden>

    Trivial typos: READMEs, gnuastro.texi
---
 README-hacking      |    2 +-
 bootstrapped/README |    6 +++---
 doc/gnuastro.texi   |    6 +++---
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/README-hacking b/README-hacking
index eecc47c..b49b2f4 100644
--- a/README-hacking
+++ b/README-hacking
@@ -86,7 +86,7 @@ you cloned 'gnuastro' directory.
 The recommended way is to clone Gnulib and the Autoconf archives separately
 (see above), then tell the script where to look for them. You will not need
 an internet connection every time you decide to bootstrap, your 'gnuastro'
-directory will be much more cleaner, and if your other packages or projects
+directory will be much cleaner, and if your other packages or projects
 need these tools, you won't need to have multiple copies. Note that during
 development, sometimes it can be convenient to remove all non-version
 controlled files.
diff --git a/bootstrapped/README b/bootstrapped/README
index 2b568d3..b9b5dfa 100644
--- a/bootstrapped/README
+++ b/bootstrapped/README
@@ -3,14 +3,14 @@ Imported files to GNU Astronomy Utilities
 
 The contents of this directory (except this README file!) are imported
 to GNU Astronomy Utilities (Gnuastro) from other projects. Therefore
-they are not maintained by Gnuastro developers and separately kept in
-this directory for clarity and easy maintainence.
+they are not maintained by Gnuastro developers and are kept separately
+in this directory for clarity and easy maintenance.
 
 In the version controlled repository this directory only contains this
 single README file. It is populated during the bootstrapping process
 (see ../README-hacking for more on bootstrapping, or the
 "Bootstrapping" section in the manual). In the distribution tar-ball
-this directory is populated with the relevant necessary files.
+this directory is populated with the necessary files.
 
 The projects that were used are:
 
diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index be99ad3..dd2bcf4 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -2868,7 +2868,7 @@ of your projects also needs Gnulib, and you insist on 
running bootstrap
 like this, you will have two copies. In case you regularly backup your
 important files, Gnulib will also slow down the backup process. Therefore
 while the simple invocation above can be used with no problem, it is not
-recommended, see the next paragraph.
+recommended. To do better, see the next paragraph.
 
 The recommended way to get these two packages is thoroughly discussed in
 @ref{Bootstrapping dependencies} (in short: clone them in the separate
@@ -18767,8 +18767,8 @@ else is already working on. In that case, you can get 
in touch with them
 and help the job go on faster, see @ref{Gnuastro project webpage}. This
 workflow is currently mostly borrowed from the general recommendations of
 
address@hidden@url{https://github.com/git/git/blob/master/Documentation/SubmittingPatches}}
-and GitHub. But since Gnuastro is under heavy development currently, these
-might change and evolve to better suite our needs.
+and GitHub. But since Gnuastro is currently under heavy development, these
+might change and evolve to better suit our needs.
 
 
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]