Study/Devops-exercises
1
0
Fork 0
mirror of https://github.com/bregman-arie/devops-exercises.git synced 2026-02-04 15:49:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos and grammatical issues in README.md (#10610)

Browse Source 
This commit corrects multiple spelling and grammar issues to improve clarity and accuracy. 
Changes include:
- "Explain what is Semaphore" → "Explain what Semaphore is"
- "disadvantges" → "disadvantages"
- "Is containerization is a type..." → "Is containerization a type..."
- "Why to used a load balancer?" → "Why to use a load balancer?"
- "Sytem Design Hero" → "System Design Hero"
This commit is contained in:
bobalice05 2025-12-27 07:20:09 -07:00 committed by GitHub
parent f42034b45a
commit 0499332fc4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -852,7 +852,7 @@ POSIX (Portable Operating System Interface) is a set of standards that define th
</b></details> </b></details>
<details> <details>
<summary>Explain what is Semaphore and what its role in operating systems.</summary><br><b> <summary>Explain what Semaphore is and what its role in operating systems.</summary><br><b>
A semaphore is a synchronization primitive used in operating systems and concurrent programming to control access to shared resources. It's a variable or abstract data type that acts as a counter or a signaling mechanism for managing access to resources by multiple processes or threads. A semaphore is a synchronization primitive used in operating systems and concurrent programming to control access to shared resources. It's a variable or abstract data type that acts as a counter or a signaling mechanism for managing access to resources by multiple processes or threads.
</b></details> </b></details>
@ -887,7 +887,7 @@ Hosted hypervisors and bare-metal hypervisors.
</b></details> </b></details>
<details> <details>
<summary>What are the advantages and disadvantges of bare-metal hypervisor over a hosted hypervisor?</summary><br><b> <summary>What are the advantages and disadvantages of bare-metal hypervisor over a hosted hypervisor?</summary><br><b>
Due to having its own drivers and a direct access to hardware components, a baremetal hypervisor will often have better performances along with stability and scalability. Due to having its own drivers and a direct access to hardware components, a baremetal hypervisor will often have better performances along with stability and scalability.
@ -903,7 +903,7 @@ Desktop virtualization
</b></details> </b></details>
<details> <details>
<summary>Is containerization is a type of Virtualization?</summary><br><b> <summary>Is containerization a type of Virtualization?</summary><br><b>
Yes, it's a operating-system-level virtualization, where the kernel is shared and allows to use multiple isolated user-spaces instances. Yes, it's a operating-system-level virtualization, where the kernel is shared and allows to use multiple isolated user-spaces instances.
</b></details> </b></details>
@ -2974,7 +2974,7 @@ A load balancer accepts (or denies) incoming network traffic from a client, and
</b></details> </b></details>
<details> <details>
<summary>Why to used a load balancer?</summary><br><b> <summary>Why to use a load balancer?</summary><br><b>
* Scalability - using a load balancer, you can possibly add more servers in the backend to handle more requests/traffic from the clients, as opposed to using one server. * Scalability - using a load balancer, you can possibly add more servers in the backend to handle more requests/traffic from the clients, as opposed to using one server.
* Redundancy - if one server in the backend dies, the load balancer will keep forwarding the traffic/requests to the second server so users won't even notice one of the servers in the backend is down. * Redundancy - if one server in the backend dies, the load balancer will keep forwarding the traffic/requests to the second server so users won't even notice one of the servers in the backend is down.