diff --git a/_posts/2013-10-26-find-whether-a-windows-dll-is-compiled-for-32-or-64-bits-on-linux.markdown b/_posts/2013-10-26-find-whether-a-windows-dll-is-compiled-for-32-or-64-bits-on-linux.markdown
index 1eb73c0..9ada606 100644
--- a/_posts/2013-10-26-find-whether-a-windows-dll-is-compiled-for-32-or-64-bits-on-linux.markdown
+++ b/_posts/2013-10-26-find-whether-a-windows-dll-is-compiled-for-32-or-64-bits-on-linux.markdown
@@ -33,14 +33,14 @@ I knew that for native linux (.so) files, objdump would be my w
So I gave it a shot, and tried:
-[bash]
+{% highlight bash %}
$ objdump -x my_windows.dll | head -n 15 # returns the first 15 lines of the result
-[/bash]
+{% endhighlight %}
And here was the result :
-[bash]
+{% highlight bash %}
libxuggle-5.dll: file format pei-i386
@@ -52,8 +52,6 @@ HAS_RELOC, EXEC_P, HAS_SYMS, HAS_LOCALS, D_PAGED
start address 0x6e741058
-
-
Characteristics 0x2306
executable
@@ -66,9 +64,7 @@ debugging information removed
DLL
-[/bash]
-
-
+{% endhighlight %}
Pretty neat, huh?
diff --git a/_posts/2013-10-30-integrate-a-twitter-timeline-in-your-android-application.markdown b/_posts/2013-10-30-integrate-a-twitter-timeline-in-your-android-application.markdown
index 4368a3d..93b692f 100644
--- a/_posts/2013-10-30-integrate-a-twitter-timeline-in-your-android-application.markdown
+++ b/_posts/2013-10-30-integrate-a-twitter-timeline-in-your-android-application.markdown
@@ -114,7 +114,7 @@ I used fill_parent because I wanted to give as much space as possible to the Web
The result is far from perfect, but it's not that bad for roughly 30 minutes of work :).
-[caption id="attachment_900" align="aligncenter" width="480"]
twitter timeline embedded into an android application[/caption]
+
On top of that, It directly allows my users to post tweets from the application (using the timeline), and will let everybody know about the BresTram twitter account.
Hopefully, this will help me get some useful feedback.