Fix KUKA guide discoverability and normalize asset naming

Author: nevalsar

…i/common-platforms/assets/friquality.png …/common-platforms/assets/fri-quality.pngwiki/common-platforms/assets/friquality.png renamed to wiki/common-platforms/assets/fri-quality.png wiki/common-platforms/assets/friquality.png renamed to wiki/common-platforms/assets/fri-quality.png

@@ -4,3 +4,8 @@ title: Common Platforms
 ---
 **This page is a stub.** You can help us improve it by [editing it](https://github.com/RoboticsKnowledgebase/roboticsknowledgebase.github.io).
 {: .notice--warning}
+
+## Key Subsections and Highlights
+
+- **[Working with KUKA LBR Med](/wiki/common-platforms/kuka/)**
+  Setup and integration guide for KUKA LBR Med with ROS 2, including Sunrise Workbench setup and FRI connection reliability notes.

wiki/common-platforms/assets/fristate.png …ki/common-platforms/assets/fri-state.pngwiki/common-platforms/assets/fristate.png renamed to wiki/common-platforms/assets/fri-state.png wiki/common-platforms/assets/fristate.png renamed to wiki/common-platforms/assets/fri-state.png

@@ -33,22 +33,22 @@ Sunrise Workbench is the IDE for developing Java applications running on the KUK
 
 Once you installed the Workbench and started a project, you need to manually install the software packages in the SunriseOS folder. From Help->Install New software, you select local as installing source, and browse toward the packages you want to install.
 
-![Sunrise Workbench](assets/sunrise_install_software.png)
+![Sunrise Workbench](assets/sunrise-install-software.png)
 
 Once you have installed the packages, in our case it solved all the missing dependencies in our existing project.
 
 Inside a project, StationSetup.cat is the file that defines the arm topology, what software should be installed into the control station, and the arm’s configuration like IP address and other parameters. The StationSetup should only be installed once, while project synchronization should be done every time you make modifications to the code.
 
-![Synchronize Project Button](assets/sunrise_workbench_synchronize.png)
+![Synchronize Project Button](assets/sunrise-workbench-synchronize.png)
 
 Because the KUKA software is proprietary, it’s not easy to find documentation online. Thus it’s hard to understand what is the function of the code. Luckily when in code editor view, if you hover over a function, it will pop out the function definition. If you want to dive deeper into the function, you can select “open attached Javadoc in a browser” to open the Javadoc that comes with the packages.
 
-![Open Javadoc Button](assets/sunrise_workbench_synchronize.png)
+![Open Javadoc Button](assets/sunrise-workbench-javadoc.png)
 
 ### Fast Robot Interface
 Fast Robot interface can stream out robot data in real-time, and when connection quality is good, it can also command the robot.
 
-![Software Architecture](assets/lbr_fri_ros2.svg)
+![Software Architecture](assets/lbr-fri-ros2.svg)
 
 (In AUT Mode) Run the LBRServer.java application from the robot pendant, and run the corresponding ROS2 node on the PC. Then the robot should be connected.
 
@@ -58,11 +58,11 @@ The purpose of the LBRServer application is to talk over the controller PC’s E
 
 Depending on the network quality, there might be issues that come up with using the LBR FRI connection issues. If the connection quality drops below a certain threshold, the ROS side of the system will kill the connection for safety reasons and crash the application. Based on the network quality, the application defines certain states, as shown below. 
 
-![Representation of the network connection states](assets/friquality.png)
+![Representation of the network connection states](assets/fri-quality.png)
 
 The system will let you monitor the state of the robot and control it as long as the connection is classified as “Good” or “Excellent”.  The behavior tree based on the connection status is as follows. You can get information about the robot’s joints if the status is MONITORING_READY, and you can give it goal values if the status is COMMANDING_ACTIVE.
 
-![System behavior tree based on the connection status](assets/fristate.png)
+![System behavior tree based on the connection status](assets/fri-state.png)
 
 If the connection status is below “GOOD” anytime, The application will shut. We had this issue happen to us during our demo. To avoid that happening in the future, we intend to modify the ROS Client to allow the robot to stay connected even if the connection is lost for a second, and we’ll implement our manipulation code in a manner to handle these situations.
 
@@ -71,4 +71,4 @@ In this wiki we covered most of the setup and usage of Kuka arm with ROS2 interf
 
 ## References
 - [LBR FRI ROS 2 GitHub Repository](https://github.com/lbr-stack/lbr_fri_ros2_stack)
-- [LBR FRI ROS 2 GitHub Online Document](https://lbr-stack.readthedocs.io/en/latest/)
+- [LBR FRI ROS 2 GitHub Online Document](https://lbr-stack.readthedocs.io/en/latest/)