Skip to content

Commit e8025ff

Browse files
NdpntMattiSG
andauthored
Improve phrasing
Co-authored-by: Matti Schneider <[email protected]>
1 parent e25a69e commit e8025ff

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/deployment/reference/server-specifications.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Approximately 750MB of storage is required for the engine itself, with the remai
1717

1818
Storage requirements typically grow at a rate of less than 0.5MB per tracked terms per month on average. This growth rate varies depending on the type of service being tracked:
1919

20-
- Large digital services, like those in the [PGA collection](https://github.com/OpenTermsArchive/pga-declarations): ~1MB per terms per month
20+
- Very large online platforms with large legal teams and heavy layouts: ~1MB per terms per month
2121
- Standard collections: ~0.1-0.3MB per terms per month
2222

2323
## Operating system
@@ -28,4 +28,4 @@ Supported operating systems:
2828

2929
## Location
3030

31-
To align with our [third design principle]({{< relref "concepts/design-principles#3-obtain-documents-like-a-user-would" >}}), servers should be deployed in geographic regions that align with the jurisdiction the collection targets. This is crucial because some services deliver different versions of documents based on the server's location, even when the documents are supposed to be identical. Therefore, ensure your server is physically located in a country within the jurisdiction that the collection targets.
31+
Servers should be physically located in geographic regions that align with the jurisdiction the collection targets to ensure to [obtain documents like a user would]({{< relref "concepts/design-principles#3-obtain-documents-like-a-user-would" >}}). This is crucial because some services deliver different versions of documents based on the location of the request, even when the documents are supposed to be identical.

0 commit comments

Comments
 (0)