Improve details about eliminating NFS usage

doc/administration/job_logs.md

@@ -150,8 +150,8 @@ server, these two locations on the file system have to be shared using NFS.
 
 To eliminate both file system requirements:
 
-- [Enable the incremental logging feature](#enable-or-disable-incremental-logging), which uses Redis instead of disk space for temporary caching of job logs.
-- Configure [object storage](job_artifacts.md#object-storage-settings) for storing archived job logs.
+1. Configure [object storage](job_artifacts.md#object-storage-settings) for storing archived job logs.
+1. [Enable the incremental logging feature](#enable-or-disable-incremental-logging), which uses Redis instead of disk space for temporary caching of job logs.
 
 ### Technical details
 

doc/administration/nfs.md

@@ -12,6 +12,8 @@ recommended for performance reasons.
 
 For data objects such as LFS, Uploads, Artifacts, and so on, an [Object Storage service](object_storage.md)
 is recommended over NFS where possible, due to better performance.
+When eliminating the usage of NFS, there are [additional steps you need to take](object_storage.md#other-alternatives-to-file-system-storage)
+in addition to moving to Object Storage.
 
 File system performance can impact overall GitLab performance, especially for
 actions that read or write to Git repositories. For steps you can use to test