Skip to content

Commit 09558e1

Browse files
committed
Update Blog “why-private-ai”
1 parent dfcb21d commit 09558e1

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

content/blog/why-private-ai.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,8 +51,7 @@ Beyond reputational risk, regulations like HIPAA and PCI forces counterparties i
5151

5252
The final example of losing control of your data is when some engineer goes and uploads a document describing trade secrets, debugs some code with a proprietary algorithm inside, or signs a waiver to download a confidential document, forgets about the waiver, and then uploads it to get a quick summary. Looking at you [Samsung](https://www.bloomberg.com/news/articles/2023-05-02/samsung-bans-chatgpt-and-other-generative-ai-use-by-staff-after-leak)
5353

54-
## \
55-
2. Model Performance
54+
## 2. Model Performance
5655

5756
I referred to this [in a previous blog](https://developer.hpe.com/blog/how-to-pick-a-large-language-model-for-private-ai/): there are two ways to measure model performance: the **speed** of the output, and the **quality** of the output.
5857

0 commit comments

Comments
 (0)