readme: change WinFetch to Winfetch

lptstr · Apr 6, 2019 · 258656b · 258656b
1 parent cbea610
commit 258656b
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
 <h3 align="center"><img src="https://lptstr.github.io/lptstr-images/proj/winfetch/logo.png" alt="logo" height="100px"></h3>
-<p align="center">A command-line system information utility for Windows</p>
+<p align="center">A command-line system information utility for Windows 10</p>
 
 <p align="center">
 <img alt="GitHub code size in bytes" src="https://img.shields.io/github/languages/code-size/lptstr/winfetch.svg">
@@ -12,15 +12,15 @@
 
 Winfetch is a command-line system information utility written in PowerShell 6 for Windows. Winfetch displays information about your operating system, software and hardware in an way similar to Neofetch and Screenfetch. 
 
-WinFetch curently supports Windows 10; Windows 7 and Windows 8 have not yet been tested. **It is highly recommended to use WinFetch with PowerShell Core**; errors may appear if any other version is used.
+Winfetch curently supports Windows 10; Windows 7 and Windows 8 have not yet been tested. **It is highly recommended to use Winfetch with PowerShell Core**; errors may appear if any other version is used.
 
-While WinFetch does work in the majority of cases, things may break occasionally. Please report all such bugs [here](https://github.com/lptstr/winfetch/issues/new).
+While Winfetch does work in the majority of cases, things may break occasionally. Please report all such bugs [here](https://github.com/lptstr/winfetch/issues/new).
 
 <img src="https://lptstr.github.io/lptstr-images/screenshots/projects/winfetch/computant-hyper.png" alt="winfetch" align="right" height="230px" width="350">
 
 Why use Winfetch?
 1. You don't have any other choices.
-2. **WinFetch isn't bloated.** The whole thing is ~13KB and 400 lines of pure PowerShell, counting comments. Compare that to Neofetch, which is about 280KB and 7,500 lines of code.
-3. **No need for the WSL, Cygwin, or MSYS2.** While you need to install the WSL (Windows Subsystem for Linux) to run Neofetch, all you need to use WinFetch is PowerShell 6 (or later), which you probably already have installed.
+2. **Winfetch isn't bloated.** The whole thing is ~15KB and 500 lines of pure PowerShell, counting comments. Compare that to Neofetch, which is about 280KB and 7,500 lines of code.
+3. **No need for the WSL, Cygwin, or MSYS2.** While you need to install the WSL (Windows Subsystem for Linux) to run Neofetch, all you need to use Winfetch is PowerShell 6 (or later), which you probably already have installed.
 
 #### More: \[[Dependencies](https://github.com/lptstr/winfetch/wiki/Dependencies)\] \[[Installation](https://github.com/lptstr/winfetch/wiki/Installation)\] \[[Usage](https://github.com/lptstr/winfetch/wiki/Basic-Usage)\]