Merge pull request #52 from sergeypanin1994/main

fix(docs): updated URLs, corrected grammar, and improved clarity across documentation

Docs/clean-install-guide.md

@@ -2,7 +2,7 @@
 
 ## Why Clean Install?
 
-As developers we install a lot of software. Every item could potentially
+As developers, we install a lot of software. Every item could potentially
 contain malware. The only way to be sure your system isn’t compromised is
 a fresh installation.
 
@@ -26,7 +26,7 @@ Before clean installing generate your clean install pack with teaBASE.
 > automatically.
 
 > [!IMPORTANT]
-> Transfer your pack external storage before clean installing! A USB key or
+> Transfer your pack to external storage before clean installing! A USB key or
 > another computer are good.
 
 Once macOS is clean installed, transfer the pack back and open it. The bundled
@@ -36,7 +36,7 @@ Once macOS is clean installed, transfer the pack back and open it. The bundled
 
 Nowadays the majority of data and settings are stored in the cloud.
 However, some apps will certainly lose settings as part of a clean install.
-The important thing is your data and dotfiles are restored.
+The important thing is that your data and dotfiles are restored.
 
 > [!NOTE]
 > You can take advantage of this to explore your apps with a clean slate.

README.md

@@ -18,7 +18,7 @@ by signing your commits.
 
 <img src='https://teaxyz.github.io/teaBASE/img/secure-dev.png' width=477>
 
-Our `gpg` signing is best in class secure with way less bloat, hassle and
+Our `gpg` signing is best-in-class secure with way less bloat, hassle and
 overhead than GNU’s GPG suite.
 
 > [!TIP]
@@ -36,7 +36,7 @@ overhead than GNU’s GPG suite.
 
 ## Git Add-Ons
 
-A [fork scaled] “package manager” for the vibrant Git ecosystem.
+A [fork-scaled] “package manager” for the vibrant Git ecosystem.
 
 <img src='https://teaxyz.github.io/teaBASE/img/git-addons.png' width=479>
 
@@ -119,7 +119,7 @@ configuration tools. If you disagree we’d like to hear your take though.
 
 ### Why is this Written in Objective-C rather than Swift?
 
-Preference Panes are old school and the continued integration of them into
+Preference Panes are old-school and the continued integration of them into
 macOS is not well documented nor well supported. We didn’t want to risk
 potential deployment hassles by choosing Swift here even though we would
 prefer Swift.

Sources/teaBASE.m

@@ -172,7 +172,7 @@ - (IBAction)onShareClicked:(id)sender {
     NSString *encodedMessage = [message stringByAddingPercentEncodingWithAllowedCharacters:[NSCharacterSet URLQueryAllowedCharacterSet]];
 
     // Construct the full URL
-    NSString *urlString = [NSString stringWithFormat:@"https://twitter.com/intent/tweet?text=%@", encodedMessage];
+    NSString *urlString = [NSString stringWithFormat:@"https://x.com/intent/tweet?text=%@", encodedMessage];
     NSURL *url = [NSURL URLWithString:urlString];
 
     // Open the URL