diff --git a/components/http_foundation/introduction.rst b/components/http_foundation/introduction.rst
index 6475fab2c0a..cdf60f39834 100644
--- a/components/http_foundation/introduction.rst
+++ b/components/http_foundation/introduction.rst
@@ -297,7 +297,7 @@ code, and an array of HTTP headers::
         array('content-type' => 'text/html')
     );
 
-These information can also be manipulated after the Response object creation::
+This information can also be manipulated after the Response object creation::
 
     $response->setContent('Hello World');
 
diff --git a/components/http_foundation/sessions.rst b/components/http_foundation/sessions.rst
index 430a83ac23c..0034963f331 100644
--- a/components/http_foundation/sessions.rst
+++ b/components/http_foundation/sessions.rst
@@ -190,8 +190,12 @@ data is an array, for example a set of tokens. In this case, managing the array
 becomes a burden because you have to retrieve the array then process it and
 store it again::
 
-    $tokens = array('tokens' => array('a' => 'a6c1e0b6',
-                                      'b' => 'f4a7b1f3'));
+    $tokens = array(
+        'tokens' => array(
+            'a' => 'a6c1e0b6',
+            'b' => 'f4a7b1f3',
+        ),
+    );
 
 So any processing of this might quickly get ugly, even simply adding a token to
 the array::
@@ -201,7 +205,7 @@ the array::
     $session->set('tokens', $tokens);
 
 With structured namespacing, the key can be translated to the array
-structure like this using a namespace character (defaults to `/`)::
+structure like this using a namespace character (defaults to ``/``)::
 
     $session->set('tokens/c', $value);