chore: update npm versioning notes

Author: NathanWalker

Diff for: understanding-packages.md

@@ -38,7 +38,9 @@ There are also quite a number of plugins maintained and developed by the NativeS
 
 NativeScript packages do not follow Semantic Versioning for a particular reason. Since NativeScript enables the empowerment of JavaScript with native platform APIs we strive to do major releases around platform API tooling upgrade cycles (Things like Xcode, Android Studio, etc.). Major/Minor releases are generally released every six months (~March and ~September which is often the timeframe platform API toolchains are also updated), while patch releases may be released as often as every week. Patch releases should never contain breaking changes, however minor and major releases can. We strive to always note any breaking changes in the Changelogs, to make upgrades as easy as possible.
 
-We always recommend using `~` (tilda) with any NativeScript package versions in your projects as that will ensure anytime you execute a `ns clean` against your project that the next run will pull down the latest patch release fixes to anything we may have released.
+### Recommended: Use tilde `~`
+
+We always recommend using tilde `~` with any NativeScript package versions in your projects to ensure anytime you execute `ns clean` against your project that the subsequent run will pull down the latest patch release fixes to anything we may have released.
 
 For example, when referencing the `@nativescript/*` packages, we always recommend the following:
 
@@ -55,3 +57,13 @@ For example, when referencing the `@nativescript/*` packages, we always recommen
 ```
 
 This will ensure bug fix patch updates are automatically installed when cleaning your projects in addition to ensuring that no major version changes may accidentally pulled it which may contain breaking changes.
+
+### When to use caret `^`?
+
+If you are comfortable with the particular npm package and are Ok handling any potential breaking changes from dependencies in your projects on your own then using a caret in front of your versions is absolutely fine.
+
+[Learn more about version specifiers here](https://github.com/npm/node-semver#tilde-ranges-123-12-1)
+
+### When to use `next`?
+
+Using `next` as the version for any NativeScript related packages will always pull down latest `main` (or `master`) changes from the repo which is likely to contain breaking changes however can be a great way to try out cutting edge features or fixes. Use `next` when you absolutely know what you are doing.