chore: Progress

Author: Youssef1313

doc/articles/controls/map-control-support.md

@@ -98,7 +98,7 @@ For the detailed procedure for Windows, please follow this link: https://msdn.mi
   + Application type
 + Hit *Create* and get the key
 
-The key will be set as the value for the parameter _MapServiceToken_ for the MapControl object.
+The key will be set as the value for the parameter *MapServiceToken* for the MapControl object.
 
 ### Android
 
@@ -119,7 +119,7 @@ The key will be set as the value for the parameter _MapServiceToken_ for the Map
 
 **Note:** For apps in production we suggest restricting the keys to be used only by your Android app. This is possible by using the SHA-1 fingerprint of your app.
 
-_For a detailed procedure on how to retrieve the SHA-1 fingerprint for your Android application, please follow this link: https://developers.google.com/maps/documentation/android-api/signup#release-cert_
+*For a detailed procedure on how to retrieve the SHA-1 fingerprint for your Android application, please follow this link: <https://developers.google.com/maps/documentation/android-api/signup#release-cert>*
 
 ## Configure your application
 

doc/articles/features/web-authentication-broker.md

@@ -8,9 +8,9 @@ uid: Uno.Features.WAB
 
 ## Usage on WebAssembly
 
-* The _redirect URI_ **MUST** be with the origin (protocol + hostname + port) of the application. It is not possible to use a custom scheme URI.
-* When using the `<iframe>` mode (see _advanced usages_ below), the server must allow for using CSP (Content Security Policy).
-* Default _redirect URI_ is `<origin>/authentication-callback`. For example `http://localhost:5000/authentication-callback`.
+* The *redirect URI* **MUST** be with the origin (protocol + hostname + port) of the application. It is not possible to use a custom scheme URI.
+* When using the `<iframe>` mode (see *advanced usages* below), the server must allow for using CSP (Content Security Policy).
+* Default *redirect URI* is `<origin>/authentication-callback`. For example `http://localhost:5000/authentication-callback`.
 * It is not possible for applications to clear cookies for the authentication server when this one is from another origin. The only way clear cookies is to deploy the app and the authentication server on the same site (sharing the same origin).
 * You can change the size and the initial title of the open window by setting corresponding settings in `WinRTFeatureConfiguration.WebAuthenticationBroker` .
 
@@ -40,11 +40,11 @@ uid: Uno.Features.WAB
   }
   ```
 
-* To use the automatic discovery of the _redirect URI_, it is required to set the `IntentFilter` using the attributes like in the previous point. If you put it in the manifest, you'll need to set the URI using the `WinRTFeatureConfiguration.WebAuthenticationBroker.DefaultReturnUri` property.
+* To use the automatic discovery of the *redirect URI*, it is required to set the `IntentFilter` using the attributes like in the previous point. If you put it in the manifest, you'll need to set the URI using the `WinRTFeatureConfiguration.WebAuthenticationBroker.DefaultReturnUri` property.
 
-* Default _redirect URI_ will be `<scheme>:/authentication-callback`. Ex: `my-app-auth:/authentication-callback`
+* Default *redirect URI* will be `<scheme>:/authentication-callback`. Ex: `my-app-auth:/authentication-callback`
 
-* The default implementation of the `WebAuthenticationBroker` on Android will launch the system browser and the result will come back through the custom scheme of the _Return Uri_. The _AndroidX Chrome Custom Tabs_ may also be used. _Advanced_ section below contains instructions about this.
+* The default implementation of the `WebAuthenticationBroker` on Android will launch the system browser and the result will come back through the custom scheme of the *Return Uri*. The *AndroidX Chrome Custom Tabs* may also be used. *Advanced* section below contains instructions about this.
 
 ## Advanced Usages
 
@@ -121,4 +121,4 @@ On WebAssembly, it is possible to use an in-application `<iframe>` instead of op
 NOTES:
 
 * The IFrame control should be present in the visual tree or the user won't see it.
-* If you want to use a _silent_ `<iframe>`, you don't need to create a control, you can simply use the `WebAuthenticationOptions.SilentMode` as the first parameter to `WebAuthenticationBroker.AuthenticateAsync()`.
+* If you want to use a *silent* `<iframe>`, you don't need to create a control, you can simply use the `WebAuthenticationOptions.SilentMode` as the first parameter to `WebAuthenticationBroker.AuthenticateAsync()`.

doc/articles/guides/open-id-connect.md

@@ -18,7 +18,7 @@ This article will document the usage of `IdentityModel.OidcClient` into an Uno a
 
 ## Demo Endpoint
 
-This code uses the _IdentityServer_ demonstration endpoint with the following parameters:
+This code uses the *IdentityServer* demonstration endpoint with the following parameters:
 
 | Field     | Value                                     |
 | --------- | ----------------------------------------- |
@@ -37,7 +37,7 @@ For platforms supporting it, the custom protocol "oidc-auth:" will be used.
 
 ## Step 1 - Add Reference to OidcClient package
 
-Add the package [`IdentityModel.OidcClient`](https://www.nuget.org/packages/IdentityModel.OidcClient) to all relevant _head_ projects of the solution.
+Add the package [`IdentityModel.OidcClient`](https://www.nuget.org/packages/IdentityModel.OidcClient) to all relevant *head* projects of the solution.
 
 ## Step 2 - Prepare for Return Uri
 
@@ -80,7 +80,7 @@ Add the `oidc-auth:` custom scheme in `Info.plist` file.
 </array>
 ```
 
-Alternatively, you can use the editor integrated in Visual Studio to set it, in the _advanced_ tab:
+Alternatively, you can use the editor integrated in Visual Studio to set it, in the *advanced* tab:
 
 ![Return Url in iOS](../Assets/features/authenticationbroker/return-url-editor.png)
 
@@ -90,7 +90,7 @@ There's nothing special for UWP. Any return Uri will work.  You can force it to
 
 **WebAssembly**
 
-There's nothing special for WASM. The default _return Uri_ of the platform (`WebAuthenticationBroker.GetCurrentApplicationCallbackUri()`) will work with this sample and will default to `<origin>/authentication-callback`. It should be something like `http://localhost:5000/authentication-callback` when running locally using Kestrel.
+There's nothing special for WASM. The default *return Uri* of the platform (`WebAuthenticationBroker.GetCurrentApplicationCallbackUri()`) will work with this sample and will default to `<origin>/authentication-callback`. It should be something like `http://localhost:5000/authentication-callback` when running locally using Kestrel.
 
 ## Step 3 - Prepare the UI
 
@@ -218,7 +218,7 @@ private async void SignOut_Clicked(object sender, RoutedEventArgs e)
 
 **IMPORTANT FOR WEBASSEMBLY**
 
-On WebAssembly, it's important to configure the linker to prevent the removal of some important part of the _OIDC Connect_ client library:
+On WebAssembly, it's important to configure the linker to prevent the removal of some important part of the *OIDC Connect* client library:
 
 `LinkerConfig.xml`:
 

doc/articles/guides/silverlight-migration/12-migrate-auth-ui.md

@@ -260,7 +260,7 @@ Let's walk through the implementation.
 
     > [!TIP]
     > As noted in the Microsoft documentation:
-    > _If your data does not undergo fine-grained changes, and if it's likely to be updated as part of a specific action, then you can make your bindings one-time, and force a manual update at any time with a call to **Update**._
+    > *If your data does not undergo fine-grained changes, and if it's likely to be updated as part of a specific action, then you can make your bindings one-time, and force a manual update at any time with a call to **Update**.*
 
 1. To add support for the login when the **OK** (or Primary) button is clicked, update the **ContentDialog_PrimaryButtonClick** method as follows:
 

doc/articles/interop/MSAL.md

@@ -27,7 +27,7 @@ To use MSAL into an Uno project, follow the following steps:
        .Build();
    ```
 
-4. Where you are using the _Interactive_ mode (`_app.AcquireTokenInteractive`), add another call to `.WithUnoHelpers()` like this:
+4. Where you are using the *Interactive* mode (`_app.AcquireTokenInteractive`), add another call to `.WithUnoHelpers()` like this:
 
    ``` csharp
    var authResult = await _app.AcquireTokenInteractive(scopes)
@@ -71,9 +71,9 @@ Particularities for WASM:
     >
     > You'll also need to register addresses for the other environments and adjust the code to use the right IDs & URIs. The redirect Uri must always be on the same hostname & port or otherwise it won't work.
 
-  * Optionally, a file in the Wasm project `wwwroot/authentication/login-callback.htm` with empty content (you could display a message like « _Please wait while the authentication process completes_ » for slower browsers).
+  * Optionally, a file in the Wasm project `wwwroot/authentication/login-callback.htm` with empty content (you could display a message like « *Please wait while the authentication process completes* » for slower browsers).
 
-* Token cache is _in-memory_ for now­. The library is not persisting the token anywhere in the browser yet. The app can save it.
+* Token cache is *in-memory* for now­. The library is not persisting the token anywhere in the browser yet. The app can save it.
 
 ## Other things
 

doc/articles/interop/wasm-javascript-1.md

@@ -18,7 +18,7 @@ Uno fully embraces HTML5 as its display backend when targeting WebAssembly (WASM
 
 In the HTML world, everything running in the browser is assets that must be downloaded from a server. To integrate existing JavaScript frameworks, they can be either download those from another location on the Internet (usually from a CDN service) or embed and deployed with the app.
 
-The Uno Bootstrapper can automatically embed any asset and deploy them with the app. Some of them (CSS & JavaScript) can also be loaded with the app. Here's how to declare them in a _Uno Wasm_ project:
+The Uno Bootstrapper can automatically embed any asset and deploy them with the app. Some of them (CSS & JavaScript) can also be loaded with the app. Here's how to declare them in a *Uno Wasm* project:
 
 1. **JavaScript files** should be in the `WasmScripts`  folder: they will be copied to the output folder and loaded automatically by the bootstrapper when the page loads. **They must be marked with the `EmbeddedResources` build action**:
 
@@ -30,7 +30,7 @@ The Uno Bootstrapper can automatically embed any asset and deploy them with the
    </ItemGroup>
    ```
 
-2. **CSS Style files** should be in the `WasmCSS` folder: they will be copied to the output folder and referenced in the _HTML head_ of the application. **They must be marked with the `EmbeddedResources` build action**.
+2. **CSS Style files** should be in the `WasmCSS` folder: they will be copied to the output folder and referenced in the *HTML head* of the application. **They must be marked with the `EmbeddedResources` build action**.
 
    ``` xml
    <!-- .csproj file -->

doc/articles/supported-features.md

@@ -63,7 +63,7 @@ uid: Uno.Development.SupportedFeatures
 
 ### Responsive Design
 
-- Layout constraints [Min/Max][Width/Height]
+- Layout constraints \[Min/Max][Width/Height]
 - Binding SourceTriggers (TextBox immediate vs. focus lost interactions)
 - DependencyProperty Inheritance (Color, text style propagation)
 

doc/articles/uno-development/listviewbase-internals.md

@@ -12,7 +12,7 @@ Before reading it, you should first read the documentation of [ListViewBase aime
 
 `ListViewBase` is the base class of `ListView` and `GridView`. The remainder of the article will refer to 'ListView', the more commonly used of the two derived controls, for ease of reading, but most of the information is applicable to `GridView` as well since a large part of the implementation is shared.
 
-`ListView` is a specialized type of [`ItemsControl`](https://docs.microsoft.com/uwp/api/windows.ui.xaml.controls.itemscontrol) designed for showing large numbers of items. `ListView` is by default _virtualized_, meaning that it only materializes view containers for those items which are visible or about to be visible within the scroll viewport. When items disappear from view, their containers are _recycled_ and reused for newly appearing views. Correctly-functioning virtualization is the key to good scroll performance.
+`ListView` is a specialized type of [`ItemsControl`](https://docs.microsoft.com/uwp/api/windows.ui.xaml.controls.itemscontrol) designed for showing large numbers of items. `ListView` is by default *virtualized*, meaning that it only materializes view containers for those items which are visible or about to be visible within the scroll viewport. When items disappear from view, their containers are *recycled* and reused for newly appearing views. Correctly-functioning virtualization is the key to good scroll performance.
 
 Other important features of `ListView`:
 
@@ -73,7 +73,7 @@ The 'life cycle' of view creation and positioning of the `ListView` largely take
     1. `UpdateLayout()` => `UnfillLayout()`. `UnfillLayout()` takes a direction, and trims materialized item containers that are not visible starting from the **opposite** direction. So to take the example above: `UnfillLayout()` would start with item 0, and see that it lies entirely outside the viewport (`-20 < 0`), so it would dematerialize it, returning it to the recycler to be reused. It would then consider item 1, see that it is partially visible (`60 > 0`), and terminate at that point. `UnfillLayout()` is particularly important during scrolling (see below).
 2. List is arranged.
     1. Android framework => `VirtualizingPanelLayout.OnLayoutChildren()` => `VirtualizingPanelLayout.UpdateLayout()`.
-    2. `UpdateLayout()` does _not_ call `ScrapLayout()` from within the arrange pass. This is because item dimensions should not have changed since the measure. It does however call `FillLayout()` and `UnfillLayout()` again. This is because the dimensions available to the list itself _might_ be different from the ones it was measured with.
+    2. `UpdateLayout()` does *not* call `ScrapLayout()` from within the arrange pass. This is because item dimensions should not have changed since the measure. It does however call `FillLayout()` and `UnfillLayout()` again. This is because the dimensions available to the list itself *might* be different from the ones it was measured with.
 3. List is scrolled.
     1. Android framework => `VirtualizingPanelLayout.ScrollVerticallyBy()` (or `ScrollHorizontallyBy()`).
     1. `ScrollVerticallyBy()` => `ScrollBy()`.