Update README.md

@@ -14,8 +14,10 @@ Get also makes navigation much clearer and more concise for beginners and friend
 
 
 Add this to your package's pubspec.yaml file:
 Add this to your package's pubspec.yaml file:
 
 
+```
 dependencies:
 dependencies:
-  get: 
+  get: ^1.3.0
+```
   
   
 And import it:
 And import it:
 ```dart
 ```dart
@@ -57,9 +59,23 @@ Get.offAll(NextScreen());
 However, for people who like more organized code who want to navigate with named routes, or for Flutter_web Developers who want the url to show exactly which route is being shown, and want the page refresh not to affect the state of the routes. On your site, we give you a much more elegant and functional solution. Yeah, the default navigation doesn't fully support Flutter_web, but Get does !!!!
 However, for people who like more organized code who want to navigate with named routes, or for Flutter_web Developers who want the url to show exactly which route is being shown, and want the page refresh not to affect the state of the routes. On your site, we give you a much more elegant and functional solution. Yeah, the default navigation doesn't fully support Flutter_web, but Get does !!!!
 
 
 ## So... Is possible used default namedRoutes from flutter?
 ## So... Is possible used default namedRoutes from flutter?
-- Yes, and with no navigation bug
+- Yes, and with no navigation bug, add "named" to Get. HOWEVER, TO MAKE THIS TYPE OF NAVIGATION, USE THE ROUTE MODEL FROM REPOSITORY. 
+Example of navigation with named routes:
+
+To navigate to nextScreen
+```dart
+Get.toNamed("/NextScreen");
+```
+To navigate and remove the previous screen from the tree.
+```dart
+Get.offNamed("/NextScreen");
+```
+To navigate and remove all previous screens from the tree.
+```dart
+Get.offAllNamed("/NextScreen");
+```
 
 
-## Using with Named Routes and And offering full flutter_web support:
+## Using with Named Routes and And offering full flutter_web support (REQUIRED FOR NAMED ROUTES):
 
 
 ### Add " navigatorKey: Get.key," to MaterialApp
 ### Add " navigatorKey: Get.key," to MaterialApp
 
 
@@ -74,13 +90,13 @@ void main() {
 }
 }
 ```
 ```
 
 
-Copy this class and put it in your app, rename routes and classes for your own, add more classes to it if necessary.
-
-### Important!!! We suggest that you copy this class for 3 reasons:
+### Important!!! COPY THE ROUTER CLASS BELOW:
+Copy this Router class below and put it in your app, rename routes and classes for your own, add more classes to it if necessary.
 
 
+We suggest that you copy this class for 3 reasons:
 1- You must define an escape route if you accidentally set a wrong route. This example already contains this.
 1- You must define an escape route if you accidentally set a wrong route. This example already contains this.
 
 
-2- Flutter_Web does not provide friendly urls or url settings (no matter how you set the route, it will always return to the main page after the page is reloaded and the route is not displayed in the url with default navigation) But Get supports it! So, when a user enters yourflutterwebsite.com/support and exactly the support route is displayed, you need to pass the settings parameter to GetRoute, and this example already contemplates it!
+2- Flutter_Web does not provide friendly urls(no matter how you set the route, it will always return to the main page after the page is reloaded and the route is not displayed in the url with default navigation), but Get supports it! So, when a user enters yourflutterwebsite.com/support and exactly the support route is displayed, you need to pass the settings parameter to GetRoute, and this example already contemplates it!
 
 
 3- These routes are designed to work with GetRoute, not CupertinoPageRoute or MaterialPageRoute. Never put them here.
 3- These routes are designed to work with GetRoute, not CupertinoPageRoute or MaterialPageRoute. Never put them here.