Commit cd456963 authored by Yuri Chornoivan's avatar Yuri Chornoivan

Fix typos and formatting

parent bdf96134
......@@ -263,7 +263,7 @@ The most important one is **reviewing changes people make**. You can do this on
1. Reviewing merge requests
You can help review merge requests. request reviewing is usually done by programmers to find mistakes in each other's code, but because programming code is text based just like regular text, we can use this to check against typos as well!
You can help review merge requests. Request reviewing is usually done by programmers to find mistakes in each other's code, but because programming code is text based just like regular text, we can use this to check against typos as well!
A merge request, is an amount of changes done in a document (added, removed) put into a machine readable file. When someone submits a review request (on system like gitlab or github this is a merge or pull request), people who maintain the original files will have to look them over and can make comments about things needing to change. This allows them to comment on things like typos, over-complicated writing but also things that are incorrect. After a patch has been accepted it can be pushed into the version control system.
......
......@@ -24,9 +24,11 @@ Pattern
Which pattern you'll be using.
Scale
The size of the pattern. 1.0 is 100%.
.. image:: /images/brushes/Krita_2_9_brushengine_texture_05.png
Horizontal Offset & Vertical Offset
How much a brush is offset, random offset sets a new per stroke.
.. image:: /images/brushes/Krita_2_9_brushengine_texture_04.png
Texturing mode
Multiply
......
......@@ -23,8 +23,9 @@ Vertical Lines
.. versionadded:: 4.2
Sort Direction
Whether to number the files using the following directions:
horizontal
left to right, top to bottom
vertical
......
.. meta::
:description:
Split Alpha: how to work with color and alpha channels of the layer seperately
Split Alpha: how to work with color and alpha channels of the layer separately
.. metadata-placeholder
......
......@@ -194,7 +194,7 @@ Autosave Every
Unnamed autosave files are hidden by default
This determines whether the filename of autosaves has a period prepended to the name. On Linux and Mac OS this is a technique to ensure the file is hidden by default.
Create Backup File
When selected Krita will, upon save, rename the original file as a backup file and save the current image to the original name. The result is that you will have saved the image, and there will be a copy of the image that is saved seperately as a backup. This is useful in case of crashes during saves.
When selected Krita will, upon save, rename the original file as a backup file and save the current image to the original name. The result is that you will have saved the image, and there will be a copy of the image that is saved separately as a backup. This is useful in case of crashes during saves.
Backup File Location
The default location these backups should be stored.
......
......@@ -7,31 +7,31 @@
:authors: - Wolthera van Hövell tot Westerflier <griffinvalley@gmail.com>
:license: GNU free documentation license 1.3 or later.
.. index:: Channel Seperation, Seperate Image
.. index:: Channel Separation, Separate Image
.. _separate_image:
Separate Image
--------------
The seperate image dialog allows you to separate the channels of the image into layers. This is useful in game texturing workflows, as well as more advanced CMYK workflows. When confirming, :guilabel:`Seperate Image` creates a series of layers for each channel. So for RGB, it will create Red, Green and Blue layers, each representing the pixels of that channel, and for CMYK, Cyan, Magenta, Yellow and Key layers.
The separate image dialog allows you to separate the channels of the image into layers. This is useful in game texturing workflows, as well as more advanced CMYK workflows. When confirming, :guilabel:`Separate Image` creates a series of layers for each channel. So for RGB, it will create Red, Green and Blue layers, each representing the pixels of that channel, and for CMYK, Cyan, Magenta, Yellow and Key layers.
Source
Which part of the image should be seperated.
Which part of the image should be separated.
Current Layer
The active layer.
Flatten all layers before seperation.
Flatten all layers before separation.
The total image.
Alpha Options
What to do with the alpha channel. All Krita images have an alpha channel, which is the transparency. How should it be handled when seperating?
What to do with the alpha channel. All Krita images have an alpha channel, which is the transparency. How should it be handled when separating?
Copy Alpha Channel to Each seperate channel as an apha channel.
Copy Alpha Channel to Each separate channel as an apha channel.
This adds the transparency of the original source to all the separation layers.
Discard Alpha Channel
Just get rid of the alpha alltogether.
Create seperate separation from alpha channel.
Create separate separation from alpha channel.
Create a separate layer with the alpha channel as a grayscale layer.
Downscale to 8bit before separating.
......
......@@ -17,7 +17,7 @@ Splits a layer according to color. This is useful in combination with the :ref:`
Put all new layers in a group layer
Put all the result layers into a new group.
Put every layer it its own, seperate group layer
Put every layer it its own, separate group layer
Put each layer into its own group.
Alpha-lock every new layer
Enable the alpha-lock for each layer so it is easier to color.
......@@ -28,6 +28,6 @@ Sort layers by amount of non-transparent pixels.
Disregard opacity.
Whether to take into account transparency of a color.
Fuzziness
How precise the algorithm should be. The large the fuzziness, the less precise the algorithm will be. This is necessary for splitting layers with anti-aliasing, because otherwise you would end up with a seperate layer for each tiny pixel.
How precise the algorithm should be. The large the fuzziness, the less precise the algorithm will be. This is necessary for splitting layers with anti-aliasing, because otherwise you would end up with a separate layer for each tiny pixel.
Palette to use for naming the layers
Select the palette to use for naming. Krita will compare the main color of a layer to each color in the palette to get the most appropriate name for it.
......@@ -176,11 +176,11 @@ Krita has :ref:`a LOT of different brush engines <category_brush_engines>`, all
.. figure:: /images/brushes/Krita_example_differentbrushengines.png
:align: center
**Left:** pixel brush, **Center:** color smudge brush, **Right:** sket ceterah brush
**Left:** pixel brush, **Center:** color smudge brush, **Right:** sketch brush
For example, the pixel-brush engine is simple and allows you to do most of your basic work, but if you do a lot of painting, the color smudge brush engine might be more useful. Even though it's slower to use than the Pixel Brush engine, its mixing of colors allows you to work faster when you need to blend and mix colors.
If you want something totally different from that, the sket ceterah brush engine helps with making messy lines, and the shape brush engine allows you to make big flats quickly. There are a lot of cool effects inside Krita's brush engines, so try them all out, and be sure to check the chapters on each.
If you want something totally different from that, the sketch brush engine helps with making messy lines, and the shape brush engine allows you to make big flats quickly. There are a lot of cool effects inside Krita's brush engines, so try them all out, and be sure to check the chapters on each.
You can configure these effects via the Brush Settings drop-down, which can be quickly accessed via :kbd:`F5`. These configurations can then be saved into presets, which you can quickly access with :kbd:`F6` or the Brush Presets docker.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment