diff --git a/best_practices/creating-the-project.rst b/best_practices/creating-the-project.rst
index 60e6db3be55..d5b3a48766a 100644
--- a/best_practices/creating-the-project.rst
+++ b/best_practices/creating-the-project.rst
@@ -33,7 +33,7 @@ to create files and execute the following commands:
 
     # Windows
     c:\> cd projects/
-    c:\projects\> php symfony.phar new blog
+    c:\projects\> php symfony new blog
 
 This command creates a new directory called ``blog`` that contains a fresh new
 project based on the most recent stable Symfony version available. In addition,
@@ -110,10 +110,10 @@ Symfony documentation uses the AppBundle name.
     There is no need to prefix the AppBundle with your own vendor (e.g.
     AcmeAppBundle), because this application bundle is never going to be
     shared.
-    
+
 .. note::
-    
-    Another reason to create a new bundle is when you're overriding something 
+
+    Another reason to create a new bundle is when you're overriding something
     in a vendor's bundle (e.g. a controller). See :doc:`/cookbook/bundles/inheritance`.
 
 All in all, this is the typical directory structure of a Symfony application
diff --git a/book/installation.rst b/book/installation.rst
index 580425ed6fd..0c77443ea2f 100644
--- a/book/installation.rst
+++ b/book/installation.rst
@@ -32,7 +32,7 @@ Open your command console and execute the following commands:
 
 .. code-block:: bash
 
-    $ sudo curl -LsS http://symfony.com/installer -o /usr/local/bin/symfony
+    $ sudo curl -LsS https://symfony.com/installer -o /usr/local/bin/symfony
     $ sudo chmod a+x /usr/local/bin/symfony
 
 This will create a global ``symfony`` command in your system.
@@ -44,7 +44,7 @@ Open your command console and execute the following command:
 
 .. code-block:: bash
 
-    c:\> php -r "readfile('http://symfony.com/installer');" > symfony
+    c:\> php -r "readfile('https://symfony.com/installer');" > symfony
 
 Then, move the downloaded ``symfony`` file to your project's directory and
 execute it as follows: