diff --git a/doc/README_FOR_APP b/doc/README_FOR_APP
index 050f519..8cc7783 100644
--- a/doc/README_FOR_APP
+++ b/doc/README_FOR_APP
@@ -21,10 +21,10 @@ There are Debian packages available for all of them but ferret. Try:
 
  # aptitude install subversion ruby rake libgettext-ruby libmocha-ruby libsqlite3-ruby rcov
 
-Ferret shall enter Debian soon (as +libferret-ruby+). until there you have two options:
+Ferret shall enter Debian soon (as <tt>libferret-ruby</tt>). until there you have two options:
 
 1. build the source package from svn://svn.debian.org/svn/pkg-ruby-extras/packages-wip/libferret-ruby
-1. install ferret via rubygems: issue +gem install ferret+ as root (you'll need to install the +rubygems+ package for it)
+1. install ferret via rubygems: issue <tt>gem install ferret</tt> as root (you'll need to install the <tt>rubygems</tt> package for it)
 
 If you have problems with the setup, use the development mailing list. In
 special its possible that the requirements list above is not complete.
@@ -70,8 +70,8 @@ Use Noosfero Tracker application at http://www.colivre.coop.br/Noosfero.
 
 == Helping with development
 
-* It's recommended that you subscribe to the "development mailing
-  list":http://ynternet.net/mailman/listinfo/noosfero
+* It's recommended that you subscribe to the development mailing
+  list: http://ynternet.net/mailman/listinfo/noosfero
 * If you have a patch, create an appropriate action item
   (bugs/requirement/enhancement) in the Tracker web (see "Reporting bugs"
   above) of type.
@@ -83,27 +83,27 @@ To prepare a release of noosfero, you must follow the steps below:
 * finish all requirements and bugs assigned to the to-be-released version
 * make sure all tests pass
 * write release notes at the version's wiki topic.
-* generate package with +rake package+. Your tarball will be under the pkg/
+* generate package with <tt>rake package</tt>. Your tarball will be under the pkg/
   directory, named as noosfero-${VERSION}.tar.gz
 * test that the package contains everything that is needed: explode the tarball
   in a temporary directory, copy config/database.yml.sqlite3 to
-  config/database.yml, and make +rake db:migrate+ and +rake test+. If
+  config/database.yml, and make <tt>rake db:migrate</tt> and <tt>rake test</tt>. If
   everything is ok, you are done. If not, maybe some files are not going into
   the tarball. See lib/tasks/package.rake, probably you'll need to change it.
 * Go to the version's wiki topic and edit it to reflect the new reality.
 * Attach the generated package to that topic.
-* create a svn tag for the released version with +rake tag+. See
+* create a svn tag for the released version with <tt>rake tag</tt>. See
   lib/tasks/svn.rake in case of any questions.
 * IMMEDIATELY change the version in lib/noosfero.rb to the next version. (e.g.
   0.2.0 -> 0.3.0)
 
-If you had any problem during these steps, you can do +rake clobber_package+ to
+If you had any problem during these steps, you can do <tt>rake clobber_package</tt> to
 completely delete the generated packages and start the process again.
 
 == Working with translations
 
-* Update translation files: +rake updatepo+. Then +svn commit+ them.
+* Update translation files: <tt>rake updatepo</tt>. Then <tt>svn commit</tt> them.
 * Send the PO files to the translators.
 * Get tha PO files back from translators, put in po/ under the correct language
-  name (e.,g. po/pt_BR/) and +svn commit+.
-* test translations: +rake makemo+ and browse the application on the web.
+  name (e.,g. po/pt_BR/) and <tt>svn commit</tt>.
+* test translations: <tt>rake makemo</tt> and browse the application on the web.
--
libgit2 0.21.2