[Fix] add missing period mark

- After removing period mark from figure captions; some paragraph left
  with no period because those paragraph has only one period and that's
  because of figure caption (see
  #1444 (comment)).
- End all bullet points with a period.

Author: Vipul Kumar

book/04-git-server/sections/hosted.asc

@@ -5,6 +5,6 @@ Doing so offers a number of advantages: a hosting site is generally quick to set
 Even if you set up and run your own server internally, you may still want to use a public hosting site for your open source code – it's generally easier for the open source community to find and help you with.
 
 These days, you have a huge number of hosting options to choose from, each with different advantages and disadvantages.
-To see an up-to-date list, check out the GitHosting page on the main Git wiki at https://git.wiki.kernel.org/index.php/GitHosting[]
+To see an up-to-date list, check out the GitHosting page on the main Git wiki at https://git.wiki.kernel.org/index.php/GitHosting[].
 
 We'll cover using GitHub in detail in <<ch06-github#ch06-github>>, as it is the largest Git host out there and you may need to interact with projects hosted on it in any case, but there are dozens more to choose from should you not want to set up your own Git server.

book/06-github/sections/2-contributing.asc

@@ -36,7 +36,7 @@ It is centered on the <<ch03-git-branching#_topic_branch>> workflow covered in <
 
 Here's how it generally works:
 
-1. Fork the project
+1. Fork the project.
 2. Create a topic branch from `master`.
 3. Make some commits to improve the project.
 4. Push this branch to your GitHub project.
@@ -107,12 +107,12 @@ To https://github.com/tonychacon/blink
  * [new branch]      slow-blink -> slow-blink
 ----
 
-<1> Clone our fork of the project locally
-<2> Create a descriptive topic branch
-<3> Make our change to the code
-<4> Check that the change is good
-<5> Commit our change to the topic branch
-<6> Push our new topic branch back up to our GitHub fork
+<1> Clone our fork of the project locally.
+<2> Create a descriptive topic branch.
+<3> Make our change to the code.
+<4> Check that the change is good.
+<5> Commit our change to the topic branch.
+<6> Push our new topic branch back up to our GitHub fork.
 
 Now if we go back to our fork on GitHub, we can see that GitHub noticed that we pushed a new topic branch up and presents us with a big green button to check out our changes and open a Pull Request to the original project.
 
@@ -270,11 +270,11 @@ To https://github.com/tonychacon/blink
    ef4725c..3c8d735  slower-blink -> slow-blink
 ----
 
-<1> Add the original repository as a remote named ``upstream''
-<2> Fetch the newest work from that remote
-<3> Merge the main branch of that repository into your topic branch
-<4> Fix the conflict that occurred
-<5> Push back up to the same topic branch
+<1> Add the original repository as a remote named ``upstream''.
+<2> Fetch the newest work from that remote.
+<3> Merge the main branch of that repository into your topic branch.
+<4> Fix the conflict that occurred.
+<5> Push back up to the same topic branch.
 
 Once you do that, the Pull Request will be automatically updated and re-checked to see if it merges cleanly.
 
@@ -359,7 +359,7 @@ You can create a task list like this:
 - [ ] Document the code
 ----
 
-If we include this in the description of our Pull Request or Issue, we'll see it rendered like <<_eg_task_lists>>
+If we include this in the description of our Pull Request or Issue, we'll see it rendered like <<_eg_task_lists>>.
 
 [[_eg_task_lists]]
 .Task lists rendered in a Markdown comment

book/06-github/sections/5-scripting.asc

@@ -107,7 +107,7 @@ image::images/scripting-04-webhook-debug.png[Webhook debug]
 
 The other great feature of this is that you can redeliver any of the payloads to test your service easily.
 
-For more information on how to write webhooks and all the different event types you can listen for, go to the GitHub Developer documentation at https://developer.github.com/webhooks/
+For more information on how to write webhooks and all the different event types you can listen for, go to the GitHub Developer documentation at https://developer.github.com/webhooks/[].
 
 ==== The GitHub API
 

book/07-git-tools/sections/replace.asc

@@ -94,7 +94,7 @@ $ echo 'Get history from blah blah blah' | git commit-tree 9c68fdc^{tree}
 The `commit-tree` command is one of a set of commands that are commonly referred to as 'plumbing' commands.
 These are commands that are not generally meant to be used directly, but instead are used by *other* Git commands to do smaller jobs.
 On occasions when we're doing weirder things like this, they allow us to do really low-level things but are not meant for daily use.
-You can read more about plumbing commands in <<ch10-git-internals#_plumbing_porcelain>>
+You can read more about plumbing commands in <<ch10-git-internals#_plumbing_porcelain>>.
 =====
 
 image::images/replace3.png[]

book/07-git-tools/sections/reset.asc

@@ -194,9 +194,9 @@ In this particular case, we still have the *v3* version of our file in a commit
 
 The `reset` command overwrites these three trees in a specific order, stopping when you tell it to:
 
-1. Move the branch HEAD points to _(stop here if `--soft`)_
-2. Make the index look like HEAD _(stop here unless `--hard`)_
-3. Make the working directory look like the index
+1. Move the branch HEAD points to _(stop here if `--soft`)_.
+2. Make the index look like HEAD _(stop here unless `--hard`)_.
+3. Make the working directory look like the index.
 
 ==== Reset With a Path
 
@@ -208,8 +208,8 @@ But the index and working directory _can_ be partially updated, so reset proceed
 So, assume we run `git reset file.txt`.
 This form (since you did not specify a commit SHA-1 or branch, and you didn't specify `--soft` or `--hard`) is shorthand for `git reset --mixed HEAD file.txt`, which will:
 
-1. Move the branch HEAD points to _(skipped)_
-2. Make the index look like HEAD _(stop here)_
+1. Move the branch HEAD points to _(skipped)_.
+2. Make the index look like HEAD _(stop here)_.
 
 So it essentially just copies `file.txt` from HEAD to the index.
 

book/07-git-tools/sections/submodules.asc

@@ -732,11 +732,11 @@ $ git commit -m "Merge Tom's Changes" <5>
 [master 10d2c60] Merge Tom's Changes
 ----
 
-<1> First we resolve the conflict
-<2> Then we go back to the main project directory
-<3> We can check the SHA-1s again
-<4> Resolve the conflicted submodule entry
-<5> Commit our merge
+<1> First we resolve the conflict.
+<2> Then we go back to the main project directory.
+<3> We can check the SHA-1s again.
+<4> Resolve the conflicted submodule entry.
+<5> Commit our merge.
 
 It can be a bit confusing, but it's really not very hard.
 

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

@@ -93,7 +93,7 @@ The two features are:
 
 As a consequence, there are two different situations to consider:
 
-1. If the `.bzrignore` file does not contain any of these two specific prefixes, then you can simply make a symbolic link to it in the repository: `ln -s .bzrignore .git/info/exclude`
+1. If the `.bzrignore` file does not contain any of these two specific prefixes, then you can simply make a symbolic link to it in the repository: `ln -s .bzrignore .git/info/exclude`.
 2. Otherwise, you must create the `.git/info/exclude` file and adapt it to ignore exactly the same files in `.bzrignore`.
 
 Whatever the case is, you will have to remain vigilant against any change of `.bzrignore` to make sure that the `.git/info/exclude` file always reflects `.bzrignore`.

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

@@ -21,9 +21,9 @@ With `RemoteSigned`, only scripts having the `ZoneIdentifier` set to `Internet`
 If you're an administrator and want to set it for all users on that machine, use `-Scope LocalMachine`.
 If you're a normal user, without administrative rights, you can use `-Scope CurrentUser` to set it only for you.
 
-More about PowerShell Scopes: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_scopes[]
+More about PowerShell Scopes: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_scopes[].
 
-More about PowerShell ExecutionPolicy: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy[]
+More about PowerShell ExecutionPolicy: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy[].
 
 To set the value of `ExecutionPolicy` to `RemoteSigned` for all users use the next command:
 
@@ -36,7 +36,7 @@ To set the value of `ExecutionPolicy` to `RemoteSigned` for all users use the ne
 
 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[]
+More information about PowerShell Gallery: https://docs.microsoft.com/en-us/powershell/scripting/gallery/overview[].
 
 [source,powershell]
 ----
@@ -83,4 +83,4 @@ Then import the module using the full path to the `posh-git.psd1` file:
 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[]
-For more details on how to customize your posh-git prompt see: https://github.com/dahlbyk/posh-git/blob/master/README.md#customization-variables[]
+For more details on how to customize your posh-git prompt see: https://github.com/dahlbyk/posh-git/blob/master/README.md#customization-variables[].

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

@@ -11,4 +11,4 @@ The features are:
 * You can use part of the Sublime Merge git client functionality from within Sublime Text.
   (This requires that Sublime Merge is installed. See: https://www.sublimemerge.com/[])
 
-The official documentation for Sublime Text can be found here: https://www.sublimetext.com/docs/3/git_integration.html[]
+The official documentation for Sublime Text can be found here: https://www.sublimetext.com/docs/3/git_integration.html[].

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

@@ -16,6 +16,6 @@ The main features are:
 ** Resolve merge conflicts.
 ** View diffs.
 * With an extension, you can also handle GitHub Pull Requests:
-  https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github[]
+  https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github[].
 
-The official documentation can be found here: https://code.visualstudio.com/Docs/editor/versioncontrol[]
+The official documentation can be found here: https://code.visualstudio.com/Docs/editor/versioncontrol[].