I was following this guide.
To install ros2-navigation, need to edit `ros2-dashing-navigation2` to `ros-dashing-navigation2`.

When I tried original command from this guide, I got error below.

```bash
$ sudo apt install ros2-dashing-navigation2
Reading package lists... Done
Building dependency tree... 50%
Building dependency tree       
Reading state information... Done
E: Unable to locate package ros2-dashing-navigation2
$ sudo apt install ros2-dashing-nav2-bringup
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package ros2-dashing-nav2-bringup
```

adding navigation2 new diagram

planner/controller properties to IDs

Minor fix for broken link in build.md file

Fix twice backtracking of path by navfn planner.

Add doxygen doc in nav2_lifecycle_manager header files

changing docker file & removing travis

fix clearing logic for near-max_obj_height instances

Re-enable dwb_plugin tests

- execute gzclient and gzserver individually
- use an argument named headless to execute gzclient

Multiple controller plugins in server for contextual control 

* Attempt to filter out generated message files from code coverage.

* Reduce the number of tests run in Travis to just a single test.

* Filter specific msg packages instead of ros_idl... directories.

* Fixing a typo in the nav_2d_msgs package name.

added ros2-devel as dependency

renamed hpp and cpp files to current bt v3 naming conventions

* added Turtlebot 3 Waffle Gazebo model with depth camera plugin

*changed the robot's shape. used box for the body and cylinder for the wheels 

* removed visuals from urdf. 

*removed meshes from the Gazebo model.

Clean shutdown of system tests

robot_spawner -> nav2_gazebo_spawner

* Switch to use action interface instead of topic.

* Shutdown nav-stack once test has been completed.

* Have lifecycle manager reset managed noded in the correct order

* Add comment about race condition on action server during shutdown

* Listener should be reset before the buffer.

* Making bt nodes separate libraries.

* Using params file to specify which plugins to use.

* Add plugin names to multi-robot params files.

Multiple planner plugins server for contextual planning