From a268b3dd0c3fd6ebc1f7df37e0e75eae29c228ea Mon Sep 17 00:00:00 2001 From: Martin Date: Fri, 3 Nov 2023 11:29:15 +0100 Subject: [PATCH] Apply suggestions from code review --- services/thumbnails/README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/services/thumbnails/README.md b/services/thumbnails/README.md index febf75f99a..cc8fb7dc2c 100644 --- a/services/thumbnails/README.md +++ b/services/thumbnails/README.md @@ -52,16 +52,14 @@ Returned: 15x10 ## Thumbnail Processors Normally, an image might get cropped when creating a preview, depending on the aspect ratio of the original image. This can have negative -impacts on previews as only a part of the image will be shown. When using an _optional_ processor in the request, cropping can be avoided by -defining on how the preview image generation will be done. The following processors are available: +impacts on previews as only a part of the image will be shown. When using an _optional_ processor in the request, cropping can be avoided by defining on how the preview image generation will be done. The following processors are available: * `resize` * `fit` * `fill` * `thumbnail` -To apply one of those, a query parameter has to be added to the request, like `?processor=fit`. If no query parameter or processor -is added, the default behaviour applies which is `resize` for gif's and `thumbnail` for all others. +To apply one of those, a query parameter has to be added to the request, like `?processor=fit`. If no query parameter or processor is added, the default behaviour applies which is `resize` for gif's and `thumbnail` for all others. ## Deleting Thumbnails