docs: Update NVENC article to revise and fix typos and whitespace.

source/docs/en/latest/technical/video-nvenc.markdown

@@ -21,14 +21,14 @@ NVIDIA NVENC
 - NVIDIA GeForce GTX Pascal (1050+), GTX/RTX Turing (1650+, 2060+), Ampere (3060+) or Ada Lovelace (4060+) series GPU or better
 - NVIDIA Graphics Driver 546.33 or later
 - Windows 10 or later
-- Limited support is available on some modern Linux Distro's
+- Limited support is available on some modern Linux distros
 
 Please note, these are not hard limits. Hardware encoding via NVENC *might* work on older series GPUs and older operating systems, but this is not officially supported.
 
 ## Enabling support
 
 <!-- .system-windows -->
-Support for the NVIDIA NVENC and NVDec is enabled in preferences on the video tab. If your system is not supported, the option will be disabled.
+Support for the NVIDIA NVENC and NVDEC is enabled in preferences on the video tab. If your system is not supported, the option will be disabled.
 <!-- /.system-windows -->
 
 <!-- .system-linux -->
@@ -39,41 +39,41 @@ On Linux, there is no preference to enable the encoder. It will be available if
 
 The following presets are available under the 'Hardware' category in the presets menu:
 
-- H.265 NVENC 2160P 4K
+- H.265 NVENC 2160p 4K
 - H.265 NVENC 1080p
 
 These are a good starting point for configuring HandBrake to use these encoders.
 
 ## Performance
 
-HandBrake supports the NVIDIA NVENC encoder and NVDEC encoder.
+HandBrake supports the NVIDIA NVENC encoder and NVDEC decoder.
 
 The CPU will still be used for:
 
-- Video decoding (If hardware decoding is turned off or unavailable) 
+- Video decoding (if hardware decoding is disabled or unavailable)
 - All video filters
 - Audio encoding
-- HandBrake's engine, A/V sync etc
-- Subtitles
+- HandBrake's core engine (audio/video sync, etc.)
+- Subtitles handling
 - Muxing
 
-These operations all happen in parallel as the job progresses. As such, it is normal to see high (or even 100%) CPU utilisation even when using NVENC.
+These operations all happen in parallel as the encode job progresses. As such, it is normal to see high (or even 100%) CPU utilization even when using NVENC.
 
-It is also common, particularly on lower-end or older hardware, for the CPU to be a bottleneck which will cause lower than expected performance. To minimize this effect, disable any filters that you do not require.
+It is also common, particularly on older and lower-end hardware, for CPU-based operations to be a bottleneck in the hardware encoding pipeline, resulting in reduced performance. To minimize this effect, disable any video filters you do not require.
 
 ## Decoder Limitations
 
-HandBrake will automatically fallback to software decoding when any filter is enabled in the pipline. This includes the crop/scale filter. 
+Since hardware decoding is usually only beneficial for directly feeding an adjacent hardware encoder, HandBrake will automatically disable hardware decoding fall back to software decoding whenever it necessary for the decoded video to make a roundtrip to the CPU and back; essentially, whenever a video filter is enabled, including the crop/scale filter.
 
 ## Advanced options
 
 The NVIDIA NVENC hardware encoder has a limited set of advanced encoder options. Generally speaking, it is not recommended to change these parameters, as the built-in presets offer a good range of options for common uses.
 
-If using HandBrake’s graphical interface, you can set the options in the `Advanced Options` field on the `Video` tab in the following format:
+When using HandBrake’s graphical interface, set the options in the `Advanced Options` field on the `Video` tab in the following format:
 
     option1=value1:option2=value2
 
-If using HandBrake’s command line interface, use the `--encopts` parameter as follows:
+When using HandBrake’s command line interface, set the options using the `--encopts` parameter as follows:
 
     --encopts="option1=value1:option2=value2"