From 4413d535a880de1ae822e3cbc8ec9ea295738b47 Mon Sep 17 00:00:00 2001 From: Majd Taby Date: Tue, 23 Dec 2025 05:41:52 -0800 Subject: [PATCH] Fix typo in Assets section of CloudKit documentation --- Sources/SQLiteData/Documentation.docc/Articles/CloudKit.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Sources/SQLiteData/Documentation.docc/Articles/CloudKit.md b/Sources/SQLiteData/Documentation.docc/Articles/CloudKit.md index 93cdb849..3f7b257f 100644 --- a/Sources/SQLiteData/Documentation.docc/Articles/CloudKit.md +++ b/Sources/SQLiteData/Documentation.docc/Articles/CloudKit.md @@ -495,8 +495,8 @@ assets. However, general database design guidelines still apply. In particular, it is not recommended to store large binary blobs in a table that is queried often. If done naively you may accidentally -large amounts of data into memory when querying your table, and further large binary blobs can -slow down SQLite's ability to efficiently access the rows in your tables. +load large amounts of data into memory when querying your table. Furthermore, large binary blobs +can slow down SQLite's ability to efficiently access the rows in your tables. It is recommended to hold binary blobs in a separate, but related, table. For example, if you are building a reminders app that has lists, and you allow your users to assign an image to a list.