Add links, minor changes in documentation

doc/articles/faq.md

@@ -23,7 +23,7 @@ Uno.UI provides the ability for developers to reuse known layout and coding tech
 
 
 ## Who makes Uno Platform?
-Uno Platform was created by Team nventive over the past 4 years.
+Uno Platform was created by [Team nventive](https://nventive.com/) over the past 4 years.
 
 ## What makes Uno Platform unique?
 The Uno Platform is the only implementation of the UWP API that runs across iOS, Android and WebAssembly. 
@@ -124,7 +124,7 @@ has [`Xamarin.Forms.StackLayout`](https://docs.microsoft.com/en-us/dotnet/api/Xa
 ## Why Mono?
 [Mono](https://github.com/mono/mono) is currently the best (and only) mobile-friendly implementation of .NET that targets iOS, Android and WebAssembly. It shares a lot -- and increasing -- of code from the BCL implementation with [.NET core](https://github.com/dotnet/core), making the runtime behavior very similar and in most cases, identical across platforms.
 
-## What do you mean by #UWPeverywhere?
+## What do you mean by [#UWPeverywhere]()?
 
 Our ultimate goal is to allow for the UWP api to run on all platforms, using Microsoft's own UWP implementation as a reference.
 
@@ -146,6 +146,12 @@ Microsoft describes it best in its [What is .NET](https://www.microsoft.com/net/
 
 ## What are the advantages of using Uno platform over Flutter/React Native/Xamarin Forms?
 
+React Native is iOS and Android only. React Native for Windows could be a possibility, but it's not part of the core.
+
+Flutter is iOS and Android only too! There are plans for desktop and web support, but still as work in progress.
+
+With UnoPlatform you have a shared code and more targets to deploy your applications.
+
 # Uno.UI Platforms Frequently Asked Questions
 
 ## Does Uno.UI support a single .NET Standard 2.0 binary model?

doc/articles/getting-started-tutorial-1.md

@@ -170,7 +170,9 @@ To run the WebAssembly (Wasm) head, select **IIS Express** and press **Ctrl+F5**
     }
     ```
 
-1. Next, we will add some base properties to bind to in our XAML. In the **Solution Explorer**, double-click **MainPage.xaml.cs** to open, then add the following code.
+We will use this converter to show an issue's date.
+
+1. Next, we will add some base properties to bind to in our XAML. In the **Solution Explorer**, in the Shared project, double-click **MainPage.xaml.cs** to open, then add the following code.
 
     ```cs
     public sealed partial class MainPage : Page
@@ -236,7 +238,7 @@ To run the WebAssembly (Wasm) head, select **IIS Express** and press **Ctrl+F5**
     }
     ```
 
-1. Now that we have some basic data to bind to, in the **Solution Explorer**, double-click **MainPage.xaml** to open, then add the following code. We will start by adding a XML Namespace for the Converters and Controls from the Microsoft Community Toolkit as shown below:
+1. Now that we have some basic data to bind to, in the **Solution Explorer**, in the Shared project, double-click **MainPage.xaml** to open, then add the following code. We will start by adding a XML Namespace for the Converters and Controls from the Microsoft Community Toolkit as shown below:
 
     ```xml
     <Page x:Class="BugTracker.MainPage"
@@ -342,7 +344,7 @@ To run the WebAssembly (Wasm) head, select **IIS Express** and press **Ctrl+F5**
     > [!IMPORTANT]
     > Take note that we have added a reference to an event handler on the ComboBox. We will add this in the next step in the code behind.
 
-1. Now that our Page is complete we can go back and add the event handlers in our code behind. This will allow us to handle changes and make necessary updates. In the **Solution Explorer**, double-click **MainPage.xaml.cs** to open, then add the following code.
+1. Now that our Page is complete we can go back and add the event handlers in our code behind. This will allow us to handle changes and make necessary updates. In the **Solution Explorer**, in the Shared project, double-click **MainPage.xaml.cs** to open, then add the following code.
 
     ```cs
     // Sets the time when we Complete or Start an issue.

doc/articles/howto-use-uno-in-xamarin-forms.md

@@ -43,7 +43,7 @@ From the code-behind, it's possible to use a ContentView control to host the Uno
 </ContentPage>
 ```
 
-and the corresponding C# code:
+... and the corresponding C# code:
 
 ```csharp
 using Windows.UI.Xaml.Controls;

doc/articles/supported-features.md

@@ -2,7 +2,7 @@
 
 ## Development flow
 
-- Uno's UWP Xaml
+- Uno's UWP XAML
     - **Windows-first development**
     - **Faster compilation** for most of the development cycle, including UI code. iOS and Android can be tested for platform-specific features.
     - Ability to develop responsive layout in Windowed mode using Windows 10.
@@ -59,21 +59,21 @@
 ### Responsive design
 
 - Layout constraints [Min/Max][Width/Height]
-- Binding SourceTriggers (TextBox immediate vs. focus lost interactions)
-- DependencyProperty Inheritance (Color, text style propagation)
+- Binding SourceTriggers (`TextBox` immediate vs. focus lost interactions)
+- `DependencyProperty` Inheritance (Color, text style propagation)
 
 ### Runtime Performance
 
-- CoreDispatcher Priority support (Large UIs performance)
+- `CoreDispatcher` Priority support (Large UIs performance)
 - `x:DeferLoadStrategy="Lazy"` and `x:Load="false"` support (responsive design performance)
 - Image explicit size support (performance)
 - Event tracing (sub-millisecond [ETL performance profiling](Assets/diagnostics.PNG))
 - Internal logging
 - Reflection-less bindings (complex UI performance)
 - Binding suspension and restoration
 - Expando Binding
-- DynamicObject Binding
-- DataTemplate and ControlTemplate reuse, pooling and prefetching
+- `DynamicObject` Binding
+- `DataTemplate` and `ControlTemplate` reuse, pooling and prefetching
 
 ### ListView
 
@@ -109,7 +109,7 @@
 - Advanced WebView support (scripting, scrolling, string, custom agent)
 - Automatic asset generation from UWP assets
 - Native element embedding
-- Panels (Grid, StackPanel with `Spacing`, RelativePanel, Canvas)
+- Panels (`Grid`, `StackPanel` with `Spacing`, `RelativePanel`, `Canvas`)
 - Custom Panels
 - Popups/Dialogs
 - Work with the usual Windows tooling

doc/articles/uno-app-solution-structure.md

@@ -24,7 +24,7 @@ Clearly understanding how shared projects work is important to using Uno effecti
 
 It's important to be aware that the code in a shared-project file is compiled separately for each platform head. This gives a great deal of flexibility, but it also means that shared code may work for one platform, but not another.
 
-For example, we decide we need to use the `Json.NET` library in our app. We install the NuGet package in our `HelloWorld.Droid` head, and add a class to our `HelloWorld.Shared` project:
+For example, we decide we need to use the [`Json.NET` library](https://www.newtonsoft.com/json) in our app. We install the NuGet package in our `HelloWorld.Droid` head, and add a class to our `HelloWorld.Shared` project:
 
 ```csharp
 using Newtonsoft.Json;

doc/articles/using-uno-ui.md

@@ -221,6 +221,8 @@ Note that the default language can be defined using the `DefaultLanguage` msbuil
 
 ## Supported Uno.UI Controls
 
+To see this controls in action, visit [UnoPlatform Playground](https://playground.platform.uno/)
+
 ### Grid
 
 The Grid control is implemented as a best effort in terms of compatibility with UWP.
@@ -344,6 +346,8 @@ The Uno.UI TextBlock supports the Text property as well as the
 
 For more information, see the [TextBlock](https://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.xaml.controls.textblock.aspx) class.
 
+---
+
 ### Custom Fonts
 
 #### Custom Fonts on Android