fix: correct terminology in K-Suite page for clarity
All checks were successful
Build and Deploy Gabriel Kaszewski Portfolio / build-and-deploy-local (push) Successful in 1m4s
All checks were successful
Build and Deploy Gabriel Kaszewski Portfolio / build-and-deploy-local (push) Successful in 1m4s
This commit is contained in:
@@ -1,7 +1,6 @@
|
|||||||
"use client";
|
"use client";
|
||||||
|
|
||||||
import Image from "next/image";
|
import Image from "next/image";
|
||||||
import Link from "next/link";
|
|
||||||
import { ExternalLink, Github } from "lucide-react";
|
import { ExternalLink, Github } from "lucide-react";
|
||||||
|
|
||||||
interface KSuiteApp {
|
interface KSuiteApp {
|
||||||
@@ -384,7 +383,7 @@ export default function KSuitePage() {
|
|||||||
<p className="text-white/70">
|
<p className="text-white/70">
|
||||||
To solve the complex challenge of inter-app communication. In K-Suite,
|
To solve the complex challenge of inter-app communication. In K-Suite,
|
||||||
a photo stored in K-Photos isn't just a file; it's an asset that can be
|
a photo stored in K-Photos isn't just a file; it's an asset that can be
|
||||||
referenced in other apps or attached to a task in the upcoming K-Mood.
|
referenced in other apps or attached to an entry in the upcoming K-Mood.
|
||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
Reference in New Issue
Block a user