diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 24a7bdc28a..6e0a618277 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -7799,8 +7799,6 @@
The smart application performs
runtime package management of RPM packages.
- This application is aware of every package database
- you want to use.
You must perform an initial setup for
smart on the target machine.
@@ -7835,8 +7833,6 @@
The opkg application performs
runtime package management of IPK packages.
- This application is aware of every package database
- you want to use.
You must perform an initial setup for
opkg on the target machine.
@@ -7852,25 +7848,12 @@
- For example, assume the following:
-
-
- An HTTP server named
- my.server exists on your
- build machine.
-
-
- The server is serving packages from a directory
- named ipk/.
-
-
- The target machine is able to use the
- i586,
- all, and
- qemux86 package
- databases.
-
-
+ As an example, suppose you are serving packages from a
+ ipk/ directory containing the
+ i586,
+ all, and
+ qemux86 databases through an
+ HTTP server named my.server.
On the target, create a configuration file
(e.g. my_repo.conf) inside the
/etc/opkg/ directory containing
@@ -7883,7 +7866,7 @@
Next, instruct opkg to fetch
the repository information:
- #opkg update
+ # opkg update
The opkg application is now able
to find, install, and upgrade packages from the
@@ -7899,10 +7882,8 @@
runtime package management of DEB packages.
This application uses a source list file to find
available package databases.
- The application is aware of every package database
- you want to use.
You must perform an initial setup for
- opkg on the target machine.
+ apt on the target machine.
@@ -7926,7 +7907,7 @@
Next, instruct the apt
application to fetch the repository information:
- #apt-get update
+ # apt-get update
After this step, apt is able
to find, install, and upgrade packages from the