* Added the topic Evaluating the clustering
How can we evaluate the clustering algorithms, based on analyzing our results.
* Fixed grammar and put in second person
This might be better put in a topic separate from C, its own topic, since the network socket interface is accessible in Java, C#, Python, PHP, NodeJS, etc. . Since the socket api is written in C itself, the system calls, and most languages will use these same C system calls, I think it still works to offer the main explanation in C, then either have an example server and client in every language PHP, Ruby, Java, C#, Obj-C, etc
* Create index.md
This file introduces flex-grow: with screen shots and code samples. As with all of my commits, this is a proper contribution effort, neither copy & paste nor a links list.
* Update index.md
Added title: 'Flex Grow' to avoid Travis CL no frontmatter error.
* Update index.md
Added labels to the code blocks.
* fix: updated individual code items & sentences
Added <code></code> tags to individual code items.
Sorry for so many commits. I just saw the styling guide.
* Create flexbox-display-flex.md (#2)
* Create flexbox-display-flex.md
This file introduces the concept of display:flex and flex-direction:[row | column].
* Rename guide/english/css/flexbox-display-flex.md to guide/english/css/flexbox-display-flex/index.md
Changed the folder structure to comply with index.md.
* Update index.md
Added title: Display Flex to avoid Travice CL no frontmatter error.
* Update index.md
Added labels to the code blocks.
* fix: update individual code items.
Added <code></code> tags to individual code items.
Sorry for so many commits. I just saw the styling guide.
* Create index.md (#4)
* Create index.md
This file contains details about flex-basis, with screenshots and code samples. As with all of my commits, this is my own work not copy & paste or a lazy linkathon.
* Update index.md
Added the title; Flex Basis, to avoid Travis CI no frontmatter error.
* Update index.md
Added labels to the code blocks.
* fix: added labels for code items
Added <code></code> labels to individual code items.
Sorry for all of the commits. I just saw the styling guide. Doing my own QC.
Removed some statements talking about the optimization potential of goto (which is mentioned but never specified), and I gave a possible use-case for goto followed by some constructs that can replace it, and ended on why goto is discouraged in C++
Added information about the memory behaviour of labels, the syntax to create a label, and where a label can actually be placed (within the same function).
* fix : add URL to a missing link
In Relevant Links (line 54), the first URL text 'Using typeof' was missing a href value. I fixed it by adding the link to a FreeCodeCamp's Javascript Debugging curriculum that introduces typeof method. (
Debugging: Use typeof to Check the Type of a Variable : https://learn.freecodecamp.org/javascript-algorithms-and-data-structures/debugging/use-typeof-to-check-the-type-of-a-variable)
* I'm a first-time open source contributor. If you have any feedback about my pull request, feel free to share it with me.
* Update guide/english/certifications/javascript-algorithms-and-data-structures/basic-algorithm-scripting/boo-who/index.md
Remove the first bullet instead of adding the link (suggested by RandellDawson)
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
Intuition is that pooling creates "fuzzier" images through subsampling (also known as down-sampling). Good example where reducing information actually makes an algorithm more efficient by reducing overfitting.
* Create index.md as initial introduction to ABAP language.
WIll continue working on the file, paragraphs and the folder.
Day to day job.
* fix/suggestions
* fix/more-formatting
* fix/more-formatting
The first advanced solution is almost identical to the intermediate one. Per "similar but better" rule, I believe the first one should be kept (or at the bare minimum, they should at least fill the same category).
Update the Code Documentation file to include specific tips for writing class and function documentation. Add an advisory about using comments excessively
* create markdown file for the article
* guide: add an article for vue router
* change some wording
* fix typo
* change some wording
* add a bit on injection router to the app
* change some wording
* add title
* fix/suggested-changes
* guide/russian/cpp/index.md translation improves
freeCodeCamp/freeCodeCamp/guide/russian/cplusplus/index.md translation improves
I've done it in more readable way and translated missing parts.
* fix: removed extra line
* Translated html comment
Translated following " Your browser is lower then IE9" , "Your browser is IE9" , "Your browser is greater then IE9" to his "Si tu navegador es mas bajo de IE9" , "Si tu navegador es IE9", "Si tu navegador es mas major de IE9".
* Fix proposed translation for clearer text
* Update index.md
Translated this "Leave some space between the h1 and the p in order to understand what are we talking about." to this " Deja espacio entre <h1> y <p> para mejor entender el codigo."
* Fix proposed translation for clearer text
Should the function names be kept in English, since it's the language developers will use for their apps? Maybe the data inside the vars can be in Spanish.
