Skip to content

Commit c530542

Browse files
dabrtmnocon
andauthored
Apply suggestions from code review
Co-authored-by: Marek Nocoń <[email protected]>
1 parent 72dfebf commit c530542

File tree

2 files changed

+1
-3
lines changed

2 files changed

+1
-3
lines changed

docs/getting_started/requirements.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -214,8 +214,6 @@ For production setups it's recommended that you use Varnish/Fastly, Redis, NFS/E
214214

215215
- For content search, Solr 8.11.1 or higher.
216216
Alternatively, Elasticsearch 7.16.2 or higher 7.x version.
217-
- The above solutions require Oracle Java/Open JDK. The minimum requirement is 8 LTS, recommended 11 LTS.
218-
Newer versions aren't supported.
219217

220218
=== "[[= product_name =]] v4.6"
221219

docs/infrastructure_and_maintenance/cache/persistence_cache.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -212,7 +212,7 @@ Several cloud providers have managed services that are easier to set up, handle
212212

213213
## Using cache service
214214

215-
Using the internal cache service allows you to use an interface and without caring whether the system is configured to place the cache on File system.
215+
Using the internal cache service allows you to use an interface and without caring whether the system is configured to place the cache in Redis or on File system.
216216
And as [[= product_name =]] requires that instances use a cluster-aware cache in cluster setup, you can safely assume your cache is shared *(and invalidated)* across all web servers.
217217

218218
!!! note

0 commit comments

Comments
 (0)