Update README.md

apps/astral/README.md

@@ -14,8 +14,8 @@ Functions
 
 The text will turn blue during calculation and then back again once complete.
 
-When you first install it, all positions will be estimated from UK as the default location and all the text will be white; from the moment you get your first GPS lock with the clock, it will save your location, recalculate accordingly and change the text to red – ideal for maintaining night vision, the calculations will also now be relevant to your location and time. If you haven’t used the GPS yet, I suggest using it outside briefly to get your first fix as the initial one can take a bit longer, although it should still just be a minute or 2 max normally.   
-Lat and Lon are saved in a file called ‘astral_config’, which is generated when you first launch the app. You can review this file if you want to confirm current coordinates or even hard set different values – although be careful doing the latter as there’s no error handling to manage bad values here so you’d have to delete the file and have the app generate a new one if that happens, also the GPS functionality will overwrite anything you put in here once it picks up your location.
+When you first install it, all positions will be estimated from UK as the default location and all the text will be white; from the moment you get your first GPS lock with the clock, it will save your location, recalculate accordingly and change the text to red, ideal for maintaining night vision, the calculations will also now be relevant to your location and time. If you have not used the GPS yet, I suggest using it outside briefly to get your first fix as the initial one can take a bit longer, although it should still just be a minute or 2 max normally.   
+Lat and Lon are saved in a file called **astral.config**. You can review this file if you want to confirm current coordinates or even hard set different values \- although be careful doing the latter as there’s no error handling to manage bad values here so you’d have to delete the file and have the app generate a new one if that happens, also the GPS functionality will overwrite anything you put in here once it picks up your location.
 
 There can currently be a slight error mainly to the Az at times due to a firmware issue for acos (arccosine) that affect spherical calculations but I have used an estimator function that gives a good enough accuracy for general observation so shouldn’t noticeably be too far off. I’ll be implementing acos for better accuracy when the fix is in a standard release and the update will still include the current estimate function to support a level of backward compatibility.
 
@@ -29,17 +29,17 @@ Additional Astronomy Targets
 ----------------------------
 There are currently 15 extra targets as default in the config file, and these were selected based on well known named objects listed in various sources as good choices for both binoculars and telescopes. The objects are processed and then 9 are displayed and ordered descendingly by altitude on the basis those higher up will have better visibility.
 
-You can input different objects rather than those listed in the galaxies/extras mode by changing the astral_config file with the relevant details for: Object name, Right Ascension and Declination, below is an example. Again, there’s little in the way of error handling to streamline the app so be sure to input these in exactly the same format as you see in the file, namely signed 6 digit values with double quotes, example:
+You can input different objects rather than those listed in the galaxies/extras mode by changing the astral.config file with the relevant details for: Object name, Right Ascension and Declination, below is an example. Again, there is little in the way of error handling to streamline the app so be sure to input these in exactly the same format as you see in the file, namely signed 6 digit values with double quotes, example:
 
 *{name: "Andromeda", ra: "004244", de: "411609", type: 3}*
 
-The type property isn't utilised as yet but relates to whether the object is (in order): a cluster, nebula or galaxy. If you try putting more than 15 or so, the clock will try processing all of them but I advise against doing that because you'll get memory errors if you put in too many. A better approach is to put a limited set in seasonally based on what's best in your location.
+The type property is not utilised as yet but relates to whether the object is (in order): a cluster, nebula or galaxy. If you try putting more than 15 or so, the clock will try processing all of them but I advise against doing that because you will get memory errors if you put in too many. A better approach is to put a limited set in seasonally based on what's best in your location.
 
 Updates & Feedback
 ------------------
 Put together, initially at least, by “Ben Jabituya”, https://jabituyaben.wixsite.com/majorinput, jabituyaben@gmail.com. Feel free to get in touch for any feature request. Also I’m not precious at all - if you know of efficiencies or improvements you could make, just put the changes in. One thing that would probably be ideal is to change some of the functions to inline C to make it faster.
 
-Credit to various sources from which I’ve literally taken source code and shoehorned to fit on the Bangle:
+Credit to various sources from which I have literally taken source code and shoehorned to fit on the Bangle:
 
 -Stephen R. Schmitt:
 https://codepen.io/lulunac27/full/NRoyxE