Fix Markdown issue as reported by Megalint

Author: ljacqu

CHANGELOG.md

@@ -1,15 +1,15 @@
 # ConfigMe Changelog
 
 ## ConfigMe 1.x
-#### 1.4.1 (2023-08-28)
+### 1.4.1 (2023-08-28)
 - `@ExportName` can be added on bean fields (previously, it was only possible on accessor methods) ([#366](https://github.com/AuthMe/ConfigMe/issues/366))
 - Bug fix: unique comment is repeated if it's in a MapProperty, ListProperty or similar ([#362](https://github.com/AuthMe/ConfigMe/issues/362))
 - Bug fix: Property at root path `""` could be defined with other properties ([#363](https://github.com/AuthMe/ConfigMe/issues/363))
 - Add getter for property type in TypeBasedProperty ([#333](https://github.com/AuthMe/ConfigMe/issues/333))
 
 :blue_book: [All changes in 1.4.1](https://github.com/AuthMe/ConfigMe/milestone/16?closed=1)
 
-#### 1.4.0 (2023-08-12)
+### 1.4.0 (2023-08-12)
 - Annotated all methods with `@NotNull` and `@Nullable` for better type inference in Kotlin ([#235](https://github.com/AuthMe/ConfigMe/pull/235), [#318](https://github.com/AuthMe/ConfigMe/issues/318))
 - Support `@Comment` on fields of bean properties ([#18](https://github.com/AuthMe/ConfigMe/issues/18))
   - Please read about [breaking changes](https://github.com/AuthMe/ConfigMe/issues/18#issuecomment-1663973493) if you extend `YamlFileResource` or other internals.
@@ -22,13 +22,13 @@
 
 :blue_book: [All changes in 1.4.0](https://github.com/AuthMe/ConfigMe/milestone/13?closed=1)
 
-#### 1.3.1 (2023-06-20)
+### 1.3.1 (2023-06-20)
 - Update SnakeYAML dependency for security reasons ([#310](https://github.com/AuthMe/ConfigMe/issues/310))
-- Introduce ShortProperty, LongProperty and FloatProperty for convenience ([#260](https://github.com/AuthMe/ConfigMe/issues/268)) 
+- Introduce ShortProperty, LongProperty and FloatProperty for convenience ([#260](https://github.com/AuthMe/ConfigMe/issues/268))
 
 :blue_book: [All changes in 1.3.1](https://github.com/AuthMe/ConfigMe/milestone/14?closed=1)
 
-#### 1.3.0 (2021-10-17)
+### 1.3.0 (2021-10-17)
 - Introduce option to NOT split paths that contain dots in the YAML file ([#214](https://github.com/AuthMe/ConfigMe/issues/214))
 - Add support for BigInteger and BigDecimal in bean properties ([#182](https://github.com/AuthMe/ConfigMe/issues/182))
 - Support map properties at root path-level properly when they are empty ([#191](https://github.com/AuthMe/ConfigMe/issues/191))
@@ -37,7 +37,7 @@
 
 :blue_book: [All changes in 1.3.0](https://github.com/AuthMe/ConfigMe/milestone/11?closed=1)
 
-#### 1.2.0 (2020-09-04)
+### 1.2.0 (2020-09-04)
 - Better ability to trigger a resave for partially valid values ([#19](https://github.com/AuthMe/ConfigMe/issues/19))
   - See [comment about breaking changes](https://github.com/AuthMe/ConfigMe/issues/19#issuecomment-569066960)
 - Indentation size and number of empty lines are now configurable in YamlFileResourceOptions ([#127](https://github.com/AuthMe/ConfigMe/issues/127))
@@ -48,7 +48,7 @@
 
 :blue_book: [All changes in 1.2.0](https://github.com/AuthMe/ConfigMe/milestone/9?closed=1)
 
-#### 1.1.0 (2019-02-27)
+### 1.1.0 (2019-02-27)
 - New property structure allowing to easily define maps and lists, see PropertyInitializer
 - Support paths written together (e.g. "path.foo") in YML files
 - Fix bug in which paths with special sequences (like numbers) cannot be read
@@ -58,15 +58,15 @@
 
 :blue_book: [All changes in 1.1.0](https://github.com/AuthMe/ConfigMe/milestone/6?closed=1)
 
-#### 1.0.1 (2018-09-08)
+### 1.0.1 (2018-09-08)
 - Support all Collection types for export values (not only lists)
   - Fixes built-in lowercase String Set property creating output which cannot be read again
 - Add getter on ConfigurationData to get all comments
 - If not defined, SettingsManagerBuilder creates a manager that uses no migration service (instead of the default one)
 
 :blue_book: [All changes in 1.0.1](https://github.com/AuthMe/ConfigMe/milestone/10?closed=1)
 
-#### 1.0 (2018-09-08)
+### 1.0 (2018-09-08)
 - Large refactoring: see [Migrating from 0.x to 1.x](https://github.com/AuthMe/ConfigMe/wiki/Migrating-from-0.x-to-1.x) for migration guide
   - Improve codebase, especially the export of values and the bean mapper ([#56](https://github.com/AuthMe/ConfigMe/issues/56))
   - Fix serialization of nested beans ([#55](https://github.com/AuthMe/ConfigMe/issues/55))
@@ -80,12 +80,12 @@
 :blue_book: [All changes in 1.0](https://github.com/AuthMe/ConfigMe/milestone/8?closed=1)
 
 ## ConfigMe 0.x
-#### 0.4.1 (2018-01-14)
+### 0.4.1 (2018-01-14)
 - Fix `Optional` fields not being able to be saved in bean properties ([#51](https://github.com/AuthMe/ConfigMe/issues/51))
 
 :blue_book: [All changes in 0.4.1](https://github.com/AuthMe/ConfigMe/milestone/7?closed=1)
 
-#### 0.4 (2017-02-19)
+### 0.4 (2017-02-19)
 - Add support for `Optional`
   - New optional property type `OptionalProperty`
   - Support `Optional<?>` fields in beans
@@ -98,7 +98,7 @@
 
 :blue_book: [All changes in 0.4](https://github.com/AuthMe/ConfigMe/milestone/4?closed=1)
 
-#### 0.3 (2016-12-23)
+### 0.3 (2016-12-23)
 - Now available from Maven Central!
   - The project package is now `ch.jalu.configme`
 - Enhance handling of bean properties
@@ -116,7 +116,7 @@
 
 :blue_book: [All changes in 0.3](https://github.com/AuthMe/ConfigMe/milestone/3?closed=1)
 
-#### 0.2.1 (2016-10-22)
+### 0.2.1 (2016-10-22)
 Bugfix release:
 - Fix YAML export of a beans property at root path
 - Allow values of bean properties to be set via SettingsManager
@@ -125,14 +125,14 @@ Bugfix release:
 :blue_book: [All changes in 0.2.1](https://github.com/AuthMe/ConfigMe/milestone/5?closed=1)
 
 
-#### 0.2 (2016-10-16)
+### 0.2 (2016-10-16)
 - Allow mapping of configurations to JavaBeans classes
 - Allow to provide comments for sections
 
 :blue_book: [All changes in 0.2](https://github.com/AuthMe/ConfigMe/milestone/2?closed=1)
 
 
-#### 0.1 (2016-09-04)
+### 0.1 (2016-09-04)
 Initial release:
 - Cleanup of previously internally used configuration management
   - Changes to make more generic

CONTRIBUTING.md

@@ -10,7 +10,7 @@ ConfigMe is managed heavily based on GitHub issues, so you're invited to open a
 code changes first, either by creating an issue or by writing in the [`#configme` channel](https://discord.com/channels/295623711485198357/1143605240520769547)
 of the AuthMe Discord server.
 
-# General conventions
+## General conventions
 
 - If you're using IntelliJ, please install the Checkstyle plugin and configure it to use the rules from 
   `.checkstyle.xml`, located in the project's root directory.
@@ -20,7 +20,7 @@ of the AuthMe Discord server.
 
 No sweat if some points aren't met since they can be addressed in pull requests, and PRs can be squashed.
 
-# Code style
+## Code style
 
 Please try to match the current code style. A few pointers:
 - Indent with spaces, not tabs
@@ -29,13 +29,13 @@ Please try to match the current code style. A few pointers:
 - Use camel-case as defined in the [Google Java style guide](https://google.github.io/styleguide/javaguide.html#s5.3-camel-case)
   (i.e. use names like `setHttpLink`, not `setHTTPLink`)
 
-## Javadoc
+### Javadoc
 
 - Use the third-person form of verbs and not the imperative: "Gets all properties" and not "Get all properties".
 - Avoid `@link` to common JDK types like `Map` or `String`. These types are visible from the method signature—manually
   linking them adds no value.
-- Try to provide context rather than just un-camel-case-ing the thing you're describing 
-  (e.g. "Gets the result" on a method "getResult" does not provide any additional information). 
+- Try to provide context rather than just un-camel-case-ing the thing you're describing
+  (e.g. "Gets the result" on a method "getResult" does not provide any additional information).
 - Do not close `<p>` tags in Javadoc text. This is in line with the JDK and Oracle's [recommendations](https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#format).
 - Do not align parameter descriptions (in the form of `@param name     the name` because of
   another longer param name).

src/test/java/ch/jalu/configme/demo/README.md

@@ -1,4 +1,4 @@
-## ConfigMe demo
+# ConfigMe demo
 
 This folder contains a small demonstration showing how ConfigMe can be used.
 You can find the config.yml file [here](https://github.com/AuthMe/ConfigMe/blob/master/src/test/resources/demo/config.yml).
@@ -13,6 +13,6 @@ are present in the config.yml file; if not, it will save the file, which trigger
 properties to be saved with their default value.
 
 You can also add a new Property field to the `TitleConfig` and see how you can immediately use it
-in your application, even without worrying about `null` values. Users with an old config.yml file 
+in your application, even without worrying about `null` values. Users with an old config.yml file
 will automatically be migrated and will find the new property with its default value next time they
 start the application.

src/test/java/ch/jalu/configme/demo/beans/README.md

@@ -1,9 +1,9 @@
-## Demo with beans
+# Demo with beans
 
 This is a demo showing how you can use a custom bean with ConfigMe. The classes `Location`,
 `User`, and `UserBase` are beans. ConfigMe can scan these classes to determine the properties
 they have and will then use the config.yml file to create new objects with the data inside
-config.yml. `BeanPropertiesDemo` creates a settings manager and uses it to get the 
+config.yml. `BeanPropertiesDemo` creates a settings manager and uses it to get the
 `DemoSettings.USER_BASE` setting.
 
 You can find the config YAML file [here](https://github.com/AuthMe/ConfigMe/blob/master/src/test/resources/demo/bean_demo_config.yml).