[FE training-materials-updates] Font fix

[Michael Opdenacker]

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=56f703f58083da900560d1fbe5989da058508db8

>---------------------------------------------------------------

commit 56f703f58083da900560d1fbe5989da058508db8
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Dec 20 19:54:35 2012 +0100

    Font fix
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


>---------------------------------------------------------------

56f703f58083da900560d1fbe5989da058508db8
 .../android-application-intents.tex                |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/slides/android-application-intents/android-application-intents.tex b/slides/android-application-intents/android-application-intents.tex
index da16259..95189c7 100644
--- a/slides/android-application-intents/android-application-intents.tex
+++ b/slides/android-application-intents/android-application-intents.tex
@@ -132,11 +132,11 @@
     to deal with broadcast intents.
   \item Their overall design is quite easy to understand: there is
     only one callback to implement: \code{onReceive}
-  \item The lifecycle is quite simple too: once the onReceive callback
+  \item The lifecycle is quite simple too: once the \code{onReceive} callback
     has returned, the receiver is considered no longer active and can
     be destroyed at any moment
   \item Thus you must not use asynchronous calls (Bind to a service
-    for example) from the onReceive callback, as there is no way
+    for example) from the \code{onReceive} callback, as there is no way
     to be sure that the object calling the callback will still be alive
     in the future.
   \end{itemize}