sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reword 'allow to' sentences

Browse Source
This commit is contained in:
Phil Davis
2023-05-18 09:48:29 +05:45
parent f19830e919
commit 4874da778c
6 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ocis/adr/0007-api-for-spaces.md
+1 -1
View File
@@ -23,7 +23,7 @@ The purpose of this new API is to give clients a very simple way to query the dy
This API is supposed to be queried often, to give clients a condensed view of the available spaces for a user, but also their eTags and cTags. Hence the clients do not have to perform a PROPFIND for every space separately.
This API would even allow to provide (WebDAV-) endpoints depending on the kind and version of the client asking for it.
This API would even allow providing (WebDAV-) endpoints depending on the kind and version of the client asking for it.
## Decision Drivers
docs/ocis/adr/0016-files-metadata.md
+1 -1
View File
@@ -57,7 +57,7 @@ Use a Database or an external key/value store to persist metadata.
### Extended File Attributes
Extended File Attributes allow to store arbitrary properties. There are 4 namespaces `user`, `system`, `trusted` and `security`. We can safely use the `user` namespace. An example attribute name would be `user.ocis.owner.id`. The linux kernel has length limits on attribute names and values.
Extended File Attributes allow storing arbitrary properties. There are 4 namespaces `user`, `system`, `trusted` and `security`. We can safely use the `user` namespace. An example attribute name would be `user.ocis.owner.id`. The linux kernel has length limits on attribute names and values.
From Wikipedia on [Extended file attributes](https://en.wikipedia.org/wiki/Extended_file_attributes#Linux):