Merge pull request #607 from ant-media/happyending1-amar

Update installing-ams-on-linux.md

Author: muratugureminoglu

docs/guides/adaptive-bitrate/adaptive-bitrate-streaming.md

@@ -17,7 +17,7 @@ Internet users have varying connection speeds, from fast broadband to congested
 
 With ABR:
 
-- Viewers always get the best possible quality for their network.
+- Viewers get best possible quality based on available bandwidth.
 - Automatic switching happens behind the scenes, improving engagement and reducing viewer drop-off.
 - Smooth playback is ensured even during network fluctuations.
 
@@ -26,7 +26,7 @@ With ABR:
 
 ## How ABR Works in Ant Media Server
 
-Ant Media Server supports ABR for all playback protocols like **WebRTC** and **HLS** streaming.
+Ant Media Server supports ABR for all playback protocols such as **WebRTC** and **HLS** streaming.
 
 | Protocol | ABR Behavior |
 |----------|--------------|
@@ -41,7 +41,7 @@ Ant Media Server supports ABR for all playback protocols like **WebRTC** and **H
 You can enable ABR from your Ant Media application settings:
 
 - Go to Applications **>** Settings **>** Adaptive Bitrate in the Ant Media Server dashboard
-- Enable adaptive streaming and add the needed resolutions.
+- Enable adaptive streaming and add the desired resolutions and bitrates. 
 
 ![](@site/static/img/adaptive-streaming/dashboardABR.png)
 
@@ -51,7 +51,7 @@ You can enable ABR from your Ant Media application settings:
 
 ## Broadcast-Level ABR Configuration
 
-Since **Ant Media Server 2.8.3**, you can configure ABR settings at the **broadcast level**. This means each stream can have its own customized ABR profiles, offering more granular control.
+As of **Ant Media Server 2.8.3**, you can configure ABR settings at the **broadcast level**. This means each stream can have its own customized ABR profiles, offering more granular control.
 
 ### Rest API Endpoint
 
@@ -80,7 +80,7 @@ curl --location 'https://domainName:5443/live/rest/v2/broadcasts/create' \
   - `height`: The vertical resolution (e.g., 240 = 240p).
   - `videoBitrate`: The target video bitrate in bits per second.
   - `audioBitrate`: The target audio bitrate in bits per second.
-  - `forceEncode`: Ensures transcoding happens even if the incoming stream matches the target resolution.
+  - `forceEncode`: Forces transcoding even when the source stream resolution matches the profile.
 :::
 
 ## Stats-Based Adaptive Bitrate Switching
@@ -100,22 +100,20 @@ This means that **WebRTC viewers** will automatically receive the best possible
 
 ## Original WebRTC or HLS Stream Behavior with ABR
 
-- There is an additional setting that influences how the original WebRTC stream is handled when ABR profiles are configured:
+- These settings decide whether the original incoming stream should be included among the ABR renditions: `useOriginalWebRTCEnabled` for **WebRTC**, and `addOriginalMuxerIntoHLSPlaylist` for **HLS**.
+- By default,
+   - **WebRTC original is excluded (false)**,
+   - **HLS original is included (true)**.
+     
 
   ```js
   "useOriginalWebRTCEnabled": false,
   ```
 
-  By default, this setting is disabled and set to false.
-
-- There is a setting that influences how the original HLS stream is handled when ABR profiles are configured:
-
   ```js
   "addOriginalMuxerIntoHLSPlaylist": true,
   ```
 
-  By default, this setting is enabled so the original resolution is also added to the HLS output.
-
 ### Behavior:
 
 - **`true`:**
@@ -140,3 +138,15 @@ When using **ABR**, it’s recommended to:
 - Regularly monitor your viewer bandwidth stats via Ant Media’s monitoring tools to fine-tune ABR settings.
 
 In order to use GPU for heavy ABR streaming, [Learn How to Enable GPU for Ant Media Server](/guides/advanced-usage/using-nvidia-gpu/).
+
+<br /><br />
+---
+
+<div align="center">
+<h2> 📶 Smooth Streams, Smart Switching — Welcome to ABR Season! 🔄 </h2>
+</div>
+
+You’ve enabled **Adaptive Bitrate Streaming**, so your viewers now get the best resolution possible for their connection — no more buffering nightmares. Custom ABR profiles + stats-based switching = streams that adapt on the fly.
+
+Your streaming game is now polished, resilient, and **ready for any network curveball!** 🚀
+

docs/guides/adaptive-bitrate/enforcing-stream-quality.md

@@ -9,7 +9,7 @@ sidebar_position: 2
 
 Ant Media Server (AMS) has the ability to force stream quality. In this guide, you'll learn what it is, how it works, and how to benefit from the stream quality feature.
 
-The client-side viewer can enforce a resolution it would like to get. Keep in mind that if you request a quality with a bitrate higher than the client's bandwidth, you may see some packet drops or pixelations.
+Viewers can enforce a resolution they would like to get. Keep in mind: if you request a quality with bitrate higher than the viewer’s bandwidth, you might see packet drops or pixelation.
 
 ## How does the adaptive bitrate work?
 
@@ -25,7 +25,7 @@ Example:
     * Above 1000kbps: In this case, a resolution of 480p is sent.
     * Less than 800kbps: In this case, a resolution of 360p is sent.
 
-The adaptive bitrate feature makes sure that the end user only gets what the server is sending out.
+The adaptive bitrate feature ensures viewers receive only which qualities the server is publishing.
 
 You can learn more about the adaptive bitrate in the previous document.
 
@@ -55,7 +55,7 @@ else if (info == "streamInformation") {
 				var streamResolutions = new Array();
 
 				obj["streamInfo"].forEach(function(entry) {
-					//It's needs to both of VP8 and H264. So it can be dublicate
+					// This supports both VP8 and H264; resolution entries might appear duplicate.
 					if(!streamResolutions.includes(entry["streamHeight"])){
 						streamResolutions.push(entry["streamHeight"]);
 					}
@@ -72,7 +72,7 @@ For more details, check out [this code snippet](https://github.com/ant-media/Str
 
 ### Enforce Quality on Client Side
 
-There is a working sample `player.html` below. When you choose a resolution, it'll force the quality. You can select the resolution, as you can see from the screenshot below. 
+There is a working sample `player.html` below. When you choose a resolution, it will force the quality. You can select the resolution, as you can see from the screenshot below. 
 
 ![](@site/static/img/adaptive-streaming/stream-quality.webp)
 
@@ -84,15 +84,15 @@ AMS also allows enforcing quality in the Web Player (play.html), similar to `pla
 
 To learn more about AMS Web Player, check **[here](https://antmedia.io/docs/guides/playing-live-stream/embedded-web-player/)**.
 
-Just change the playOrder to play stream with WebRTC, HLS, DASH, or LL-HLS. The stream quality can be selected in the same way.
+Adjust the playOrder setting to choose among WebRTC, HLS, DASH, or LL-HLS. Users can then select quality similarly via the Web Player.
 
 ![](@site/static/img/adaptive-streaming/stream-quality-web-player.webp)
 
 ### Enforcing Quality for M3U8 HLS URL
 
-Since some users play the HLS directly via M3U8, you can enforce stream quality by requesting a specific HLS variant. This can be achieved by selecting the appropriate `.m3u8` file that corresponds to the desired quality.
+Since some users access HLS by specifying a particular `.m3u8` URL, you can enforce stream quality by selecting the variant corresponding to that quality.”
 
-For example, if your HLS playlist has multiple bit rates:
+For example, if your HLS playlist has multiple bitrates:
 
 * adaptive.m3u8
     * 240p
@@ -131,3 +131,14 @@ For example:
 ```
 https://domain:5443/live/streams/ll-hls/stream1/480/stream1__lowlatency.m3u8
 ```
+
+<br /><br />
+---
+
+<div align="center">
+<h2> 🎯 Your Stream, Your Quality, Your Way! 📺 </h2>
+</div>
+
+You’ve enabled **Enforced Stream Quality**, meaning viewers can pick (or you can push) exact resolutions via WebRTC, HLS, DASH, or LL-HLS. No guesswork: **what’s requested is what’s played.**
+
+Now your streams aren’t **just adaptive** — they **follow the quality rules you set.** ✅

docs/guides/adaptive-bitrate/forceencode.md

@@ -5,7 +5,7 @@ keywords: [Adaptive Bitrate Streaming, ABR, multi-bitrate streaming, live stream
 sidebar_position: 4
 ---
 
-ForceEncode is a feature of Adaptive Bitrate Streaming that transcodes all resolutions on the server by default.
+ForceEncode is an ABR feature that ensures all resolutions are transcoded on the server by default, providing consistent quality across all streams.
 
 By default, if two ABRs are enabled, such as 1080p and 720p, and the user publishes the RTMP stream in 1080p, the HLS will include all three resolutions, including the original one, resulting in two 1080p, including the transcoded one.
 
@@ -82,3 +82,15 @@ test.m3u8
 :::
 
 Using this feature allows you to save bandwidth and resources.
+
+<br /><br />
+---
+
+<div align="center">
+<h2> 🎯 You are a Smart Encoder ⚙️ </h2>
+</div>
+
+With ForceEncode, you have the power to optimize your server's performance. By **selectively transcoding streams**, you can balance quality and resource usage effectively.
+
+Your streaming setup is now more efficient, **delivering high-quality content without overloading your server!** 🚀
+

docs/guides/adaptive-bitrate/generating-thumbnails.md

@@ -13,15 +13,16 @@ Thumbnails are small, lightweight versions of images or videos, used as previews
 
 Ant Media Server can generate thumbnails (previews) of the incoming streams on the fly. This guide will help you learn configuration parameters for generating and using thumnails.
 
-- In order to activate thumbail generation, you just need to add at least one adaptive bitrate. You can do that in the dashboard using ```Application > live > Settings > Add New Bitrate```
+- To activate thumbnail generation, add at least one adaptive bitrate. You can do that in the dashboard using ```Application > live > Settings > Add New Bitrate```
 
 ![](@site/static/img/preview_1.png)
 
-- You can enable the thumbnail feature from the web panel settings by enabling the `Generate Preview` checkbox:
+- Enable the thumbnail feature from the web panel settings by checking the 'Generate Preview' checkbox:
 
  ![](@site/static/img/enable-preview.png)
 
-- You can also enable it via Advance application settings as well. Go to the ```Application > Your App > Settings  > click on    basic > switch to Advance``` and search for `generatePreview` and set it to true.
+- You can also enable it via Advanced application settings as well.
+- Go to the ```Application > Your App > Settings > click on basic > Switch to Advanced``` and search for `generatePreview` and set it to true.
 
   ```js
   "generatePreview": true,
@@ -86,7 +87,7 @@ As an alternative, you can also enable this feature on the web panel by enabling
 
 ## Preview Thumbnail
 
-The generated thumbnails will be available in this URL template:
+Access the generated thumbnails via the following URL template:
 
 ```html
 http://<SERVER_NAME>:5080/live/previews/<STREAM_ID>.png
@@ -113,3 +114,16 @@ The absolute path of the preview image is as follows:
 ```
 
 In addition to this, you can also upload thumbnail images to the S3 buckets. Please [check out the instructions for S3 Integration](https://antmedia.io/docs/category/s3-recording-and-integration/).
+
+
+<br /><br />
+---
+
+<div align="center">
+<h2> 📸 Thumbnails delivered 🎯 </h2>
+</div>
+
+With **thumbnail previews enabled**, your viewers get a sneak peek before they dive in. Whether it's a **snapshot** of the action or a glimpse of the content, these **previews** enhance the browsing experience.
+
+Your streams are now not just watched; **they're previewed, engaged with, and remembered!** 🚀
+

docs/guides/advanced-usage/activate-ams-within-restricted-geo-locations.md

@@ -5,9 +5,9 @@ keywords: [Activate AMS within self-hosted proxy server, restricted geo location
 sidebar_position: 12
 ---
 
-# Activate Ant Media Server from within restricted geo locations
+# Activate Ant Media Server in Restricted Geographies
 
-Ant Media uses Google services to verify the license key and those services are banned in China and Hong Kong. 
+Ant Media uses Google services to verify the license key, which are banned in China and Hong Kong. 
 
 For this reason, it’s not possible to verify the Ant Media license key using Google services.
 
@@ -17,14 +17,14 @@ In this article, I'll provide two options to get around these restrictions and e
 
 The two options are:
 
-- A proxy service that is provided free for Ant Media Enterprise users.
+- A proxy service, provided free for Ant Media Enterprise users.
 - A self-hosted proxy server
 
 ## 1. Free Proxy service for Enterprise Users
 
 Ant Media offers this to Enterprise users for free. To access the free service, simply send an email to support@antmedia.io to receive a username and password.
 
-After receiving a username and password, run the following command then restart the Ant Media Server.
+After receiving a username and password, run the following command, then restart the Ant Media Server.
 
 ```
 echo "proxy.address=username:password@license-verification.antmedia.io:80" >> /usr/local/antmedia/conf/red5.properties
@@ -114,3 +114,15 @@ systemctl restart antmedia
 ```
 You can now go to the Dashboard and enter your license key in the settings. 
 
+<br /><br />
+---
+
+<div align="center">
+<h2> 🔓 License Verified, Barriers Bypassed! 🌍 </h2>
+</div>
+
+You’ve enabled **proxy support** (either free or self-hosted) so your Ant Media Server can verify its **license—even from within restricted regions**. No more blocked verification, no more frustration.
+
+Your setup is now licensed, connected, and unstoppable — wherever you are! 🚀
+
+

docs/guides/advanced-usage/overcoming-restricted-networks-webrtc-ams.md

@@ -29,7 +29,7 @@ systemctl daemon-reload
 sudo setcap 'cap_net_bind_service=+ep' /usr/bin/turnserver
 ```
 
-3. Get a certificate for your domain. (TLS/TCP does not work in Let's Encrpyt Coturn due to socket buffer operation error) 
+3. Obtain a certificate for your domain. (TLS/TCP does not work in Let's Encrypt Coturn due to socket buffer operation error) 
 
 4. Update the TURN server configuration file (/etc/turnserver.conf) with these parameters:
 
@@ -92,3 +92,15 @@ turnServerCredential=your-turn-server-password
 
 Setting up a TURN server and configuring it with Ant Media Server allows you to seamlessly use WebRTC in restricted networks where only HTTP/HTTPS ports are open. This solution ensures uninterrupted communication with the outside world, enabling reliable video streaming through Ant Media Server.
 
+<br /><br />
+---
+
+<div align="center">
+<h2> 🔐 WebRTC, No Walls — TURNed On and Talking! 🌐 </h2>
+</div>
+
+With **TURN configured and AMS adjusted**, your WebRTC streams now flow even when all **you’ve got are HTTP/HTTPS channels**. TURN over TLS/TCP is punching through the restrictions.
+
+Streams are **no longer blocked—they’re resilient, connected, and unstoppable.** 🎯
+
+

docs/guides/advanced-usage/turn-instalation/coturn-quick-installation.md

@@ -112,3 +112,15 @@ turnutils_uclient -v -t -T -u username -w password -p 3478 turn_server_ip
 
 To use your TURN server with Ant Media, check out this
 [Guide](https://antmedia.io/docs/guides/configuration-and-testing/configuring-stun-turn-addresses/)
+
+<br /><br />
+---
+
+<div align="center">
+<h2> 🔄 TURN-Up the Connectivity — Firewalls, NATs, You're No Match! ⚡️ </h2>
+</div>
+
+With **coTURN** installed and configured, even the strictest **firewalls and NATs can't stop your streams**. Your communication gets relayed when needed, keeping everything smooth and seamless.
+
+**Your network just got smarter** — reliable, resilient, and ready for any connection challenge! 🚀
+

docs/guides/advanced-usage/turn-instalation/turn-load-balancing.md

@@ -55,7 +55,7 @@ We always prefer to install the Database Server on a separate server and we choo
 
         apt-get update && apt-get install mariadb-server -y
 
-*   Edit the following file ```/etc/mysql/mariadb.conf.d/50-server.cnf``` with your favorite editor such as ```vim``` or ```nano``` Please add the following lines then save and exit:
+*   Edit the following file ```/etc/mysql/mariadb.conf.d/50-server.cnf``` with your favorite editor, such as ```vim``` or ```nano``` Please add the following lines then save and exit:
 
         bind-address            = 0.0.0.0
         innodb_file_format=Barracuda
@@ -109,7 +109,7 @@ In this section, we will install and configure CoTurn on Coturn1 and Coturn2 ser
 
     ```vim /etc/turnserver.conf```
 
-*   Add below lines then save and exit. Keep in mind that we did set the password ```coturn123``` and we use them below. If you change the password, use your own instead of ```coturn123```below.
+*   Add the lines below, then save and exit. Keep in mind that we did set the password ```coturn123``` and we use them below. If you change the password, use your own instead       of ```coturn123```below.
 
         fingerprint
         lt-cred-mech
@@ -121,7 +121,7 @@ In this section, we will install and configure CoTurn on Coturn1 and Coturn2 ser
 
     ![](@site/static/img/coturn-2.png)
 
-*   Import SQL schema(```/usr/share/coturn/schema.sql```) to the database server. The file /usr/share/coturn/schema.sql is in one of the turn servers. Upload to the database server and ```schema.sql```is imported.
+*   Import SQL schema(```/usr/share/coturn/schema.sql```) to the database server. The file /usr/share/coturn/schema.sql is in one of the turn servers. Upload to the database        server and ```schema.sql```is imported.
 
     ```scp -r /usr/share/coturn/schema.sql root@192.168.1.200:```
 
@@ -153,4 +153,15 @@ You can use the following command to check that DNS Round-Robin is working corre
 
 ![](@site/static/img/coturn-nslookup.png)
 
-If you have any questions, please just drop a line to contact (at) antmedia.io
+If you have any questions, please just drop a line to contact (at) antmedia.io
+
+<br /><br />
+---
+
+<div align="center">
+<h2> ⚙️ TURN, The Traffic Manager 🌐 </h2>
+</div>
+
+You’ve set up **CoTurn** with DNS **Round Robin** and shared **MySQL userdb** — now multiple TURN servers handle your traffic evenly. Requests get distributed, auth stays consistent, and there's no single chokepoint.
+
+Your TURN setup is now resilient, **balanced**, and ready to scale! 🚀