[FAB-5479] - Clean up images

Remove externally linked images in arch-deep-dive
add images to source
[ci-skip]

Change-Id: I814c939e1e56ea10a50a1e5a3bbdb29025918e16
Signed-off-by: Nick Gaski <ngaski@us.ibm.com>

Author: nickgaski

docs/source/arch-deep-dive.rst

@@ -229,7 +229,7 @@ transactions for inclusion in the blockchain state.
 
 **Partitioning (ordering service channels).** Ordering service may
 support multiple *channels* similar to the *topics* of a
-publish/subscribe (pub/sub) messaging system. Clients can connects to a
+publish/subscribe (pub/sub) messaging system. Clients can connect to a
 given channel and can then send messages and obtain the messages that
 arrive. Channels can be thought of as partitions - clients connecting to
 one channel are unaware of the existence of other channels, but clients
@@ -590,13 +590,10 @@ conclusion whether a transaction contained in a blob is valid. Hence,
 all peers commit and apply the same sequence of transactions and update
 their state in the same way.
 
-.. figure:: http://vukolic.com/hyperledger/flow-4.png
+.. image:: images/flow-4.png
    :alt: Illustration of the transaction flow (common-case path).
 
-   Illustration of the transaction flow (common-case path).
-
-Figure 1. Illustration of one possible transaction flow (common-case
-path).
+*Figure 1. Illustration of one possible transaction flow (common-case path).*
 
 3. Endorsement policies
 -----------------------
@@ -723,11 +720,12 @@ peer does this by itself (e.g., by using the bitmask associated with
 ``PeerLedger``). A vBlock is defined as a block without the invalid
 transactions, that have been filtered out. Such vBlocks are inherently
 dynamic in size and may be empty. An illustration of vBlock construction
-is given in the figure below. |Illustration of the transaction flow
-(common-case path).|
+is given in the figure below.
+
+.. image:: images/blocks-3.png
+   :alt: Illustration of vBlock formation
 
-Figure 2. Illustration of validated ledger block (vBlock) formation from
-ledger (``PeerLedger``) blocks.
+*Figure 2. Illustration of validated ledger block (vBlock) formation from ledger (PeerLedger) blocks.*
 
 vBlocks are chained together to a hash chain by every peer. More
 specifically, every block of a validated ledger contains:
@@ -828,7 +826,5 @@ also be combined:
       checkpoint if confirmed by *f+1* different peers collocated with
       orderers.
 
-.. |Illustration of the transaction flow (common-case path).| image:: http://vukolic.com/hyperledger/blocks-3.png
-
 .. Licensed under Creative Commons Attribution 4.0 International License
    https://creativecommons.org/licenses/by/4.0/