Add empty lines accordingly common format

Author: Morganov

book/09-git-and-other-scms/sections/client-bzr.asc

@@ -10,6 +10,7 @@ Nevertheless, it is possible to work on a Bazaar repository from a Git one.
 There are many projects that allow you to use Git as a Bazaar client.
 Here we'll use Felipe Contreras' project that you may find at https://github.com/felipec/git-remote-bzr[].
 To install it, you just have to download the file git-remote-bzr in a folder contained in your `$PATH`:
+
 [source,console]
 ----
 $ wget https://raw.github.com/felipec/git-remote-bzr/master/git-remote-bzr -O ~/bin/git-remote-bzr
@@ -24,10 +25,11 @@ That's all!
 It is simple to use.
 It is enough to clone a Bazaar repository prefixing it by `bzr::`.
 Since Git and Bazaar both do full clones to your machine, it's possible to attach a Git clone to your local Bazaar clone, but it isn't recommended.
-It's much easier to attach your Git clone directly to the same place your Bazaar clone is attached to ‒ the central repository.
+It's much easier to attach your Git clone directly to the same place your Bazaar clone is attached to -- the central repository.
 
 Let's suppose that you worked with a remote repository which is at address `bzr+ssh://developer@mybazaarserver:myproject`.
 Then you must clone it in the following way:
+
 [source,console]
 ----
 $ git clone bzr::bzr+ssh://developer@mybazaarserver:myproject myProject-Git
@@ -36,6 +38,7 @@ $ cd myProject-Git
 
 At this point, your Git repository is created but it is not compacted for optimal disk use.
 That's why you should also clean and compact your Git repository, especially if it is a big one:
+
 [source,console]
 ----
 $ git gc --aggressive
@@ -45,18 +48,21 @@ $ git gc --aggressive
 
 Bazaar only allows you to clone branches, but a repository may contain several branches, and `git-remote-bzr` can clone both.
 For example, to clone a branch:
+
 [source,console]
 ----
 $ git clone bzr::bzr://bzr.savannah.gnu.org/emacs/trunk emacs-trunk
 ----
 
 And to clone the whole repository:
+
 [source,console]
 ----
 $ git clone bzr::bzr://bzr.savannah.gnu.org/emacs emacs
 ----
 
 The second command clones all the branches contained in the emacs repository; nevertheless, it is possible to point out some branches:
+
 [source,console]
 ----
 $ git config remote-bzr.branches 'trunk, xwindow'
@@ -99,6 +105,7 @@ However, be careful with its creation because with Git it is impossible to re-in
 
 To fetch the changes of the remote, you pull changes as usually, using Git commands.
 Supposing that your changes are on the `master` branch, you merge or rebase your work on the `origin/master` branch:
+
 [source,console]
 ----
 $ git pull --rebase origin
@@ -110,6 +117,7 @@ Because Bazaar also has the concept of merge commits, there will be no problem i
 So you can work on a branch, merge the changes into `master` and push your work.
 Then, you create your branches, you test and commit your work as usual.
 You finally push your work to the Bazaar repository:
+
 [source,console]
 ----
 $ git push origin master

book/09-git-and-other-scms/sections/import-bzr.asc

@@ -52,6 +52,7 @@ Traceback (most recent call last):
 ImportError: No module named fastimport
 $ pip install fastimport
 ----
+
 If it is not available, you can download it at address https://pypi.python.org/pypi/fastimport/.
 
 In the second case (on Windows), `bzr-fastimport` is automatically installed with the standalone version and the default installation (let all the checkboxes checked).

book/A-git-in-other-environments/sections/powershell.asc

@@ -12,7 +12,9 @@ It looks like this:
 image::images/posh-git.png[PowerShell with Posh-git.]
 
 ==== Installation
+
 ===== Prerequisites (Windows only)
+
 Before you're able to run PowerShell scripts on your machine, you need to set your local ExecutionPolicy to RemoteSigned (Basically anything except Undefined and Restricted).
 If you choose AllSigned instead of RemoteSigned, also local scripts (your own) need to be digitally signed in order to be executed.
 With RemoteSigned, only Scripts having the "ZoneIdentifier" set to Internet (were downloaded from the web) need to be signed, others not.
@@ -24,19 +26,22 @@ More about PowerShell Scopes: https://docs.microsoft.com/en-us/powershell/module
 More about PowerShell ExecutionPolicy: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy[]
 
 [source,powershell]
------
+----
 > Set-ExecutionPolicy -Scope LocalMachine -ExecutionPolicy RemoteSigned -Force
------
+----
 
 ===== PowerShell Gallery
+
 If you have at least PowerShell 5 or PowerShell 4 with PackageManagement installed, you can use the package manager to install posh-git for you.
 
 More information about PowerShell Gallery: https://docs.microsoft.com/en-us/powershell/scripting/gallery/overview[]
+
 [source,powershell]
------
+----
 > Install-Module posh-git -Scope CurrentUser -Force
 > Install-Module posh-git -Scope CurrentUser -AllowPrerelease -Force # Newer beta version with PowerShell Core support
------
+----
+
 If you want to install posh-git for all users, use "-Scope AllUsers" instead and execute the command from an elevated PowerShell console.
 If the second command fails with an error like `Module 'PowerShellGet' was not installed by using Install-Module`, you'll need to run another command first:
 
@@ -49,25 +54,29 @@ Then you can go back and try again.
 This happens, because the modules that ship with Windows PowerShell are signed with a different publishment certificate.
 
 ===== Update PowerShell Prompt
+
 To include git information in your prompt, the posh-git module needs to be imported.
 To have posh-git imported every time PowerShell starts, execute the Add-PoshGitToProfile command which will add the import statement into you $profile script.
 This script is executed everytime you open a new PowerShell console.
 Keep in mind, that there are multiple $profile scripts.
 E. g. one for the console and a separate one for the ISE.
+
 [source,powershell]
------
+----
 > Import-Module posh-git
 > Add-PoshGitToProfile -AllHosts
------
+----
 
 ===== From Source
+
 Just download a posh-git release from (https://github.com/dahlbyk/posh-git[]), and uncompress it.
 Then import the module using the full path to the posh-git.psd1 file:
+
 [source,powershell]
------
+----
 > Import-Module <path-to-uncompress-folder>\src\posh-git.psd1
 > Add-PoshGitToProfile -AllHosts
------
+----
 
 This will add the proper line to your `profile.ps1` file, and posh-git will be active the next time you open PowerShell.
 For a description of the Git status summary information displayed in the prompt see: https://github.com/dahlbyk/posh-git/blob/master/README.md#git-status-summary-information[]