Skip to content

Commit fa50e84

Browse files
committed
Grammatically updated the readme
1 parent e223e15 commit fa50e84

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
This repository is intended for the development of so-called "extra" modules,
44
contributed functionality. New modules quite often do not have stable API,
5-
and they are not well-tested. Thus, they shouldn't be released as a part of
5+
and they are not well-tested. Thus, they shouldn't be released as a part of the
66
official OpenCV distribution, since the library maintains binary compatibility,
77
and tries to provide decent performance and stability.
88

@@ -33,7 +33,7 @@ $ cmake -DOPENCV_EXTRA_MODULES_PATH=<opencv_contrib>/modules -DBUILD_opencv_lega
3333

3434
If you also want to build the samples from the "samples" folder of each module, also include the "-DBUILD_EXAMPLES=ON" option.
3535

36-
If you prefer using the gui version of cmake (cmake-gui), then, you can add `opencv_contrib` modules within `opencv` core by doing the following:
36+
If you prefer using the GUI version of CMake (cmake-gui), then, you can add `opencv_contrib` modules within `opencv` core by doing the following:
3737

3838
1. Start cmake-gui.
3939

@@ -55,6 +55,6 @@ If you prefer using the gui version of cmake (cmake-gui), then, you can add `ope
5555

5656
In order to keep a clean overview containing all contributed modules, the following files need to be created/adapted:
5757

58-
1. Update the README.md file under the modules folder. Here, you add your model with a single line description.
58+
1. Update the README.md file under the modules folder. Here, you add your model with a single-line description.
5959

60-
2. Add a README.md inside your own module folder. This README explains which functionality (separate functions) is available, links to the corresponding samples and explains in somewhat more detail what the module is expected to do. If any extra requirements are needed to build the module without problems, add them here also.
60+
2. Add a README.md inside your own module folder. This README explains which functionality (separate functions) is available, links to the corresponding samples, and explains in somewhat more detail what the module is expected to do. If any extra requirements are needed to build the module without problems, add them here also.

0 commit comments

Comments
 (0)