Add ribbon to README-SAMPLES.md. Fixing typos.

README-CONAN.md

@@ -206,7 +206,7 @@ Profile :=    msvc{Edition}{Type}{Bits}
 Edition :=  { 2019    | 2017  |  2015  }
 Type    :=  { Release | Debug }
 Bits    :=  { 64      | 32    }  
-Examples:     msvc2019Release64 msvc2017Release64  msvc2015Debug32
+Examples:     msvc2019Release64 msvc2017Release32  msvc2015Debug32
 ```
 
 The profile msvc2019Release64 is as follows:
@@ -242,7 +242,7 @@ In the step-by-step guide, the command `$ cmake ..` uses
 the default CMake generator.  Always use the generator for your version of Visual Studio.  For example:
 
 ```bat
-c:\..\build> conan install .. --build missing --profile msvc2019Release
+c:\..\build> conan install .. --build missing --profile msvc2019Release64
 c:\..\build> cmake         .. -G "Visual Studio 16 2019"
 c:\..\build> cmake --build .  --config Release
 ```
@@ -260,7 +260,7 @@ CMake provides Generators for different editions of Visual Studio.  The 64 and 3
 
 | | Visual Studio 2019 | Visual Studio 2017 | Visual Studio 2015|
 |:---------|--------------------|--------------------|--------------|
-| _**conan install .. --profile**_ | msvc2019Release | msvc2017Release64 | msvc2015Release64 |
+| _**conan install .. --profile**_ | msvc2019Release64 | msvc2017Release64 | msvc2015Release64 |
 | _**cmake -G**_                   |  "Visual Studio 16 2019"    |  "Visual Studio 15 2017 Win64"    | "Visual Studio 14 2015 Win64" |
 | _**profile**_<br><br><br><br><br><br><br>_ | arch=x86\_64<br>arch\_build=x86\_64<br>build\_type=Release<br>compiler.runtime=MD<br>compiler.version=16<br>compiler=Visual Studio<br>os=Windows<br>os\_build=Windows  | arch=x86\_64<br>arch\_build=x86\_64<br>build\_type=Release<br>compiler.runtime=MD<br>compiler.version=15<br>compiler=Visual Studio<br>os=Windows<br>os\_build=Windows  | arch=x86\_64<br>arch\_build=x86\_64<br>build\_type=Release<br>compiler.runtime=MD<br>compiler.version=14 <br>compiler=Visual Studio<br>os=Windows<br>os\_build=Windows |
 
@@ -276,7 +276,7 @@ CMake provides Generators for different editions of Visual Studio.  The 64 and 3
 || Visual Studio 2019 | Visual Studio 2017 | Visual Studio 2015 |
 |:-----------|--------------------|--------------------|--------------------|
 | _**conan install .. --profile**_ | msvc2019Release32 | msvc2017Release32 | msvc2015Release32 |
-| _**cmake -G**_ | "Visual Studio 15 2019" -A Win32 | "Visual Studio 15 2017" | "Visual Studio 14 2015" |
+| _**cmake -G**_ | "Visual Studio 16 2019" -A Win32 | "Visual Studio 15 2017" | "Visual Studio 14 2015" |
 | _**profile**_<br>_ | arch=x86<br>arch\_build=x86 | arch=x86<br>arch\_build=x86 | arch=x86<br>arch\_build=x86 |
 
 ##### Static Builds
@@ -303,7 +303,7 @@ You should link everything with the dynamic or static run-time. You can link a s
 It is recommended that you use profiles provided in `<exiv2dir>\cmake\msvc_conan_profiles`.
 
 You can modify profile settings on the command line.
-The following example demonstrates making substantial changes to profile settings by performing a 32 bit build using Visual Studio 2015 with a 2017 profile!  This example is not considered good practice, it is an illustration to some conan flexibility which be useful when your build environment is automated.
+The following example demonstrates making substantial changes to profile settings by performing a 32 bit build using Visual Studio 2015 with a 2017 profile!  This example is not considered good practice, it is an illustration of some conan flexibility which may be useful when your build environment is automated.
 
 ```bash
 $ conan install .. --profile msvc2017Release64 -s arch_build=x86 -s arch=x86 -s compiler.version=14

README-SAMPLES.md

@@ -1,3 +1,7 @@
+| Travis        | AppVeyor      | GitLab| Codecov| Repology| Chat |
+|:-------------:|:-------------:|:-----:|:------:|:-------:|:----:|
+| [![Build Status](https://travis-ci.org/Exiv2/exiv2.svg?branch=0.27-maintenance)](https://travis-ci.org/Exiv2/exiv2) | [![Build status](https://ci.appveyor.com/api/projects/status/d6vxf2n0cp3v88al/branch/0.27-maintenance?svg=true)](https://ci.appveyor.com/project/piponazo/exiv2-wutfp/branch/0.27-maintenance) | [![pipeline status](https://gitlab.com/D4N/exiv2/badges/0.27-maintenance/pipeline.svg)](https://gitlab.com/D4N/exiv2/commits/0.27-maintenance) | [![codecov](https://codecov.io/gh/Exiv2/exiv2/branch/0.27-maintenance/graph/badge.svg)](https://codecov.io/gh/Exiv2/exiv2) | [![Packaging status](https://repology.org/badge/tiny-repos/exiv2.svg)](https://repology.org/metapackage/exiv2/versions) | [![#exiv2-chat on matrix.org](matrix-standard-vector-logo-xs.png)](https://matrix.to/#/#exiv2-chat:matrix.org) |
+
 ![Exiv2](exiv2.png)
 
 # Exiv2 Sample Applications
@@ -652,4 +656,4 @@ Read an XMP packet from a file, parse and re-serialize it.
 
 Robin Mills<br>
 robin@clanmills.com<br>
-Revised: 2020-05-17
+Revised: 2020-11-20

README.md

@@ -55,7 +55,7 @@ The file ReadMe.txt in a build bundle describes how to install the library on th
     2. [macOS](#5-2)
     3. [MinGW/msys2](#5-3)
     4. [Cygwin](#5-4)
-    5. [Microsoft Visual C++](#5-5)
+    5. [Visual Studio](#5-5)
     6. [Unix](#5-6)
 
 [TOC](#TOC)
@@ -1175,11 +1175,11 @@ endlocal
 [TOC](#TOC)
 <div id="5-5">
 
-### 5.5 Microsoft Visual C++
+### 5.5 Visual Studio
 
-We recommend that you use Conan to build Exiv2 using Microsoft Visual C++. Exiv2 v0.27 can be built with Visual Studio versions 2008 and later.  We actively support and build with Visual Studio 2015, 2017 and 2019.
+We recommend that you use Conan to build Exiv2 using Visual Studio. Exiv2 v0.27 can be built with Visual Studio versions 2008 and later.  We actively support and build with Visual Studio 2015, 2017 and 2019.
 
-As well as Microsoft Visual Studio, you will need to install CMake, Python3, and Conan.
+As well as Visual Studio, you will need to install CMake, Python3, and Conan.
 
 1) Binary installers for CMake on Windows are availably from [https://cmake.org/download/](https://cmake.org/download/).<br/>
 2) Binary installers for Python3 are available from [python.org](https://python.org)<br/>