This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a commit to branch fix-indent
in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit 7bf630893dec4cc79f854df5c8906eb97f63731b
Author: Michael Osipov <micha...@apache.org>
AuthorDate: Thu May 16 21:57:59 2024 +0200
Fix section indents
---
content/markdown/code-quality-management.md | 4 ++--
content/markdown/community.md | 20 ++++++++--------
content/markdown/developers/conventions/jira.md | 20 ++++++++--------
.../developers/release/maven-core-release.md | 28 +++++++++++-----------
content/markdown/docs/history.md.vm | 18 +++++---------
content/markdown/extensions/index.md | 10 ++++----
content/markdown/glossary.md | 2 +-
.../guides/mini/guide-multiple-modules-4.md | 2 +-
.../guides/mini/guide-resolver-transport.md | 2 +-
content/markdown/issue-management.md | 2 +-
content/markdown/maven-1.x-eol.md | 2 +-
content/markdown/maven-conventions.md | 2 +-
content/markdown/maven-logging.md | 2 +-
content/markdown/privacy-policy.md | 2 +-
content/markdown/release-notes-all.md.vm | 2 +-
content/markdown/repository-management.md | 8 +++----
content/markdown/repository/layout.md | 2 +-
content/markdown/security.md | 14 +++++------
content/markdown/settings.md | 2 +-
content/markdown/what-is-maven.md | 2 +-
20 files changed, 70 insertions(+), 76 deletions(-)
diff --git a/content/markdown/code-quality-management.md
b/content/markdown/code-quality-management.md
index 76fd15ac..b05a5e67 100644
--- a/content/markdown/code-quality-management.md
+++ b/content/markdown/code-quality-management.md
@@ -1,4 +1,4 @@
-## Code Quality Management
+# Code Quality Management
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
@@ -22,7 +22,7 @@ Some existing Maven plugins use code analysis technologies
(like
page lists technologies and platforms that know how to aggregate all
this information to offer enhanced quality management functionalities.
-### Quality management technologies and platforms
+## Quality management technologies and platforms
Following is an alphabetical list of those we've heard mentioned around
the Maven community:
diff --git a/content/markdown/community.md b/content/markdown/community.md
index d30328b6..961e0aaa 100644
--- a/content/markdown/community.md
+++ b/content/markdown/community.md
@@ -1,4 +1,4 @@
-## The Maven Community
+# The Maven Community
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
@@ -24,39 +24,39 @@ and assist other users in need. This is a quick guide
outlining
what members of the Maven community can do to make the system work
better for everyone.
-### Helping With Maven
+## Helping With Maven
There is already a comprehensive [Guide to Helping With
Maven](./guides/development/guide-helping.html). That guide focuses upon
beginning as a supporter, with information on how to help the coding
effort.
-#### Commit Questions or Answers to the Maven User FAQ
+### Commit Questions or Answers to the Maven User FAQ
If you find things which are not correct or could be
explained in a better way or you simply miss things
do not hesitate to contact the maven community via
the users mailing list and tell us about it.
-#### Help Log Defects in JIRA
+### Help Log Defects in JIRA
Just as any other healthy project requires a quick turn-around on
defects, and a transparent method of users to have their wishes heard,
so too does Maven need your help. Refer to the [Issue
Management](./issue-management.html) page.
-#### Developers
+### Developers
For Maven developers, committers, PMC: there is a [Developers
Guide](./developers/index.html).
-### Being a Good Maven Citizen
+## Being a Good Maven Citizen
The concept of a public repository built into the core architecture of
Maven makes it necessarily community-centric. There are a few simple
things that Maven users may do to help keep that community thriving.
-#### Be a Kind Public Repository User
+### Be a Kind Public Repository User
The best thing that a user can do is to set up their own remote
repository mirror containing the projects needed: this is called a
@@ -74,18 +74,18 @@ Please take only the jars you need. We understand this is
may entail
more work, but grabbing more than 1,7 TiB of binaries really kills our
servers.
-### User Gathering Spots
+## User Gathering Spots
These are a few of the watering holes around which Maven users tend to
gather.
-#### Mailing Lists
+### Mailing Lists
Maven has a number of [Mailing Lists](./mailing-lists.html), and the Maven
User List is specifically dedicated to answering questions about all
Maven things.
-#### Slack
+### Slack
For people actively contributing to Maven, especially committers, there
is [the ASF Slack workspace](https://infra.apache.org) available to discuss
diff --git a/content/markdown/developers/conventions/jira.md
b/content/markdown/developers/conventions/jira.md
index 30f7ea1d..851b1c91 100644
--- a/content/markdown/developers/conventions/jira.md
+++ b/content/markdown/developers/conventions/jira.md
@@ -1,4 +1,4 @@
-## Maven JIRA Conventions
+# Maven JIRA Conventions
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
@@ -19,7 +19,7 @@ under the License.
-->
This document describes how Maven developers should use JIRA, our issue
management system.
-### When To Create a JIRA Issue?
+## When To Create a JIRA Issue?
This section discusses when to create a JIRA issue versus just committing a
change in Git (eventually through a PR).
@@ -32,28 +32,28 @@ of more than 100 lines, should have JIRA tickets.
Creating a JIRA issue and referring it in the commit comments simplifies
tracking the changes that happen in a release,
using JIRA automatic release notes creation.
-### How To Use Issue Details?
+## How To Use Issue Details?
This section presents some conventions about the issue fields.
-#### Priority
+### Priority
Committers have the responsibility to realign priority by editing the issue.
*Reasoning*: having a correct release note
-#### Assignee
+### Assignee
Committers can assign an issue to a specific committer that person seems to
be well placed to address it.
-#### Component/s
+### Component/s
Committers have the responsibility to specify the correct component by editing
the issue.
*Reasoning*: having a correct release note.
-#### Affects Version/s
+### Affects Version/s
By default, the Maven team considers that an issue which affects a given
version also affects preceding versions. For example, an issue
that affects Maven 3.6.3 also affects 3.6.0, 3.6.1, 3.6.2.
@@ -61,15 +61,15 @@ If it is a regression, the committers should specify the
affected versions.
*Reasoning*: having a correct release note.
-#### Fix Version/s
+### Fix Version/s
Update to correct version after merging to master.
-#### Time Tracking
+### Time Tracking
The Maven team doesn't use this. Committers can if it helps them.
-### Further Links
+## Further Links
- [JIRA
Documentation](https://confluence.atlassian.com/jira064/jira-documentation-720411693.html)
- [What is an
Issue?](https://confluence.atlassian.com/jira064/what-is-an-issue-720416138.html)
diff --git a/content/markdown/developers/release/maven-core-release.md
b/content/markdown/developers/release/maven-core-release.md
index 1d9d77f7..88031a74 100644
--- a/content/markdown/developers/release/maven-core-release.md
+++ b/content/markdown/developers/release/maven-core-release.md
@@ -1,4 +1,4 @@
-## Releasing Maven
+# Releasing Maven
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
@@ -47,7 +47,7 @@ version. The tag that produced the failed released is left in
place for
posterity. So if the release of, say, 3.2.4 fails then we move forward
with 3.2.5.
-### Produce Release Candidates
+## Produce Release Candidates
For non-alpha/beta releases, release candidates are produced before the actual
release.
@@ -67,7 +67,7 @@ After a reasonable time without regressions found, a wider
audience may be polle
Once happy with a release candidate, the full release is performed, with the
final version in place.
-### Produce the Release
+## Produce the Release
To produce a final release, the same process as for standard projects is
followed:
@@ -75,7 +75,7 @@ To produce a final release, the same process as for standard
projects is followe
Below describes the additional steps that need to be taken at the points where
the website are updated in those instructions.
-#### Prepare the Release Notes
+### Prepare the Release Notes
Checkout Maven site source <https://github.com/apache/maven-site.git>.
@@ -84,7 +84,7 @@ Create the release notes:
- create `content/markdown/docs/$version`
- create `content/markdown/docs/$version/release-notes.md` (see other versions
for an example)
-#### Stage the Latest Documentation
+### Stage the Latest Documentation
Once the release is prepared, but before the release vote, the site needs to
be staged.
@@ -97,11 +97,11 @@ mvn scm-publish:publish-scm
This will publish the Maven core site in [/ref/3-LATEST](/ref/3-LATEST).
-### Complete the release
+## Complete the release
After a successful vote you should do the following steps to finish the
release.
-#### Add New Version to ASF Distribution Directory
+### Add New Version to ASF Distribution Directory
In addition to promoting the repository, the release archives should be
moved to the release svnpubsub tree:
@@ -110,11 +110,11 @@ moved to the release svnpubsub tree:
svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/$VERSION
https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Publish Maven
$VERSION Distribution Archives"
```
-#### Update the DOAP Information
+### Update the DOAP Information
Edit <https://github.com/apache/maven/blob/master/doap_Maven.rdf> to list the
new release.
-#### Update the Web Site
+### Update the Web Site
Checkout Maven site source <https://github.com/apache/maven-site.git>.
@@ -124,7 +124,7 @@ Next, update release history
`content/markdown/docs/history.md.vm`.
Only deploy the site once the release is present on the mirrors, and the
reference documentation has been deployed to [/ref/](/ref).
-#### Deploy the Latest Documentation to Target Versioned Location
+### Deploy the Latest Documentation to Target Versioned Location
The reference documentation for Maven core source code references and API docs
has been staged in a previous step: now it needs to be deployed to its
dedicated directory before deploying the web site pointing to the new version.
@@ -134,21 +134,21 @@ This consists in copying in website svn tree the staging
/ref/3-LATEST directory
svn cp https://svn.apache.org/repos/asf/maven/website/components/ref/3-LATEST
https://svn.apache.org/repos/asf/maven/website/components/ref/$VERSION -m
"Maven $VERSION released"
```
-### Information on `/ref/current` mechanism
+## Information on `/ref/current` mechanism
The redirection from `/ref/current` to actual Maven version reference is done
through `.htaccess` published in site.
-#### Deploying the Release Website
+### Deploying the Release Website
Once both of the above have synced to the main site and a suitable number of
mirrors, proceed to update the web site and produce the announcement.
Commit your changes and then [deploy the main Maven
site](../website/deploy-maven-website.html).
-#### Remove Old Versions from ASF Distribution Directory
+### Remove Old Versions from ASF Distribution Directory
Next, any superseded releases should be removed from the above locations
(after confirming that they exist in /www/archive.apache.org/dist/maven).
-#### Proceed with Announcement
+### Proceed with Announcement
You can now proceed with the steps outlined after deploying the website on
[Maven Project Common Release Procedure](./maven-project-release-procedure.html)
diff --git a/content/markdown/docs/history.md.vm
b/content/markdown/docs/history.md.vm
index cbd8557f..7c2515ae 100644
--- a/content/markdown/docs/history.md.vm
+++ b/content/markdown/docs/history.md.vm
@@ -1,5 +1,4 @@
# Maven Releases History
-
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
@@ -17,9 +16,6 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-
- NOTE: For help with the syntax of this file, see:
- http://maven.apache.org/doxia/references/apt-format.html
-->
#set ( $archive = 'https://mail-archives.apache.org/mod_mbox/maven-' )
#macro ( release $date $version $announce $bold $jdk $rowspan )
@@ -59,8 +55,6 @@ $b_</td>
</tr>
#end
-## Maven Releases History
-
The Apache Maven team maintains the last version of the last two series of GA
releases.
If the last release is 3.9.6, the Apache Maven team project will maintain core
versions:
- 3.9.6
@@ -69,9 +63,9 @@ If the last release is 3.9.6, the Apache Maven team project
will maintain core v
Currently, plugins provide Maven API compatibility down to **3.2.5**.
New plugin releases will require Maven **3.6.3** or later.
-Date format is: YYYY-MM-DD
+Date format is YYYY-MM-DD
-<h3><a name="Maven_40">Maven 4.0+</a></h3>
+$esc.h$esc.h Maven 4.0+
<table>
<tr><th>Release Date</th>
<th>Version</th>
@@ -94,7 +88,7 @@ Date format is: YYYY-MM-DD
</table>
-<h3><a name="Maven_38">Maven 3.8.x+</a></h3>
+$esc.h$esc.h Maven 3.8.x+
<table>
<tr><th>Release Date</th>
<th>Version</th>
@@ -122,7 +116,7 @@ Date format is: YYYY-MM-DD
</table>
-<h3><a name="Maven_3">Maven 3.6.x and before</a></h3>
+$esc.h$esc.h Maven 3.6.x and before
<p>Maven before 3.6.3 has now reached its end of life.
New plugin releases will require Maven 3.6.3 or later.
@@ -172,7 +166,7 @@ The following information is made available for
reference.</p>
</table>
-<h3><a name="Maven_2">Maven 2</a></h3>
+$esc.h$esc.h Maven 2
<p>Maven 2.x has now reached its <a href="../maven-2.x-eol.html">end of
life</a>.
The following <a href="/archives/maven-2.x/index.html">Maven 2.x specific
documentation</a> is archived for reference.</p>
<table>
@@ -201,7 +195,7 @@ The following information is made available for
reference.</p>
</table>
-<h3><a name="Maven_1">Maven 1</a></h3>
+$esc.h$esc.h Maven 1
<p>Maven 1.x has now reached its <a href="../maven-1.x-eol.html">end of
life</a>.
<a href="/archives/maven-1.x/index.html">Maven 1.x documentation</a> is
archived for reference.</p>
#macro ( announce $date $version $page )
diff --git a/content/markdown/extensions/index.md
b/content/markdown/extensions/index.md
index c4575e06..fb38b1ab 100644
--- a/content/markdown/extensions/index.md
+++ b/content/markdown/extensions/index.md
@@ -1,4 +1,4 @@
-## Available Extensions
+# Available Extensions
<!--
Licensed to the Apache Software Foundation (ASF) under one
@@ -25,18 +25,18 @@ it is possible to hook into Maven, e.g. to manipulate the
lifecycle.
* [Configure Extensions](/guides/mini/guide-using-extensions.html)
* [Write Extensions](/examples/maven-3-lifecycle-extensions.html)
-### Maintained By The Maven Project
+## Maintained By The Maven Project
| Extension | Version | Release Date |
Description
| Source Repository
| Issue Tracker
|------------------------------------------------|---------|--------------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------|
|[Build Cache](./maven-build-cache-extension/) | 1.1.0 | 2023-11-27 |
Maven Incremental Build and Cache (local and remote). |
[Git](https://gitbox.apache.org/repos/asf/maven-build-cache-extension.git) /
[GitHub](https://github.com/apache/maven-build-cache-extension/) | [Jira
MBUILDCACHE](https://issues.apache.org/jira/browse/MBUILDCACHE)
|[Enforcer](/enforcer/maven-enforcer-extension/) | 3.4.1 | 2023-09-07 |
Environmental constraint checking (Maven Version, JDK etc), User Custom Rule
Execution. | [Git](https://gitbox.apache.org/repos/asf/maven-enforcer.git) /
[GitHub](https://github.com/apache/maven-enforcer/) | [Jira
MENFORCER](https://issues.apache.org/jira/browse/MENFORCER)
-### Outside The Maven Land
+## Outside The Maven Land
A number of other projects provide their own Maven extensions. This includes:
-#### Open Source
+### Open Source
| Extension | Maintainer
| Description
|-----------------------------------------------------------|---------------------|-----------
@@ -47,7 +47,7 @@ A number of other projects provide their own Maven
extensions. This includes:
| [smart-builder](https://github.com/takari/takari-smart-builder) | Takari
| The Takari Smart Builder is a replacement scheduling projects builds in a
Maven multi-module build.
|
[opentelemetry-maven-extension](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/maven-extension)
| The OpenTelemetry project | The OpenTelemetry Maven Extension
instruments builds to gather execution details as traces for build performance
optimization and for troubleshooting. <br/>OpenTelemetry traces can be
visualized in open source observability solutions such as [Jaeger
Tracing](https://www.jaegertracing.io) as well as in commercial solutions.
-#### Commercial
+### Commercial
| Extension |
Maintainer | Description
|--------------------------------------------------------------------------|-------------|-----------
diff --git a/content/markdown/glossary.md b/content/markdown/glossary.md
index 6030e5ca..be97c98b 100644
--- a/content/markdown/glossary.md
+++ b/content/markdown/glossary.md
@@ -1,4 +1,4 @@
-## Glossary
+# Glossary
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
diff --git a/content/markdown/guides/mini/guide-multiple-modules-4.md
b/content/markdown/guides/mini/guide-multiple-modules-4.md
index 0ecfbdaa..3f71c11d 100644
--- a/content/markdown/guides/mini/guide-multiple-modules-4.md
+++ b/content/markdown/guides/mini/guide-multiple-modules-4.md
@@ -1,4 +1,4 @@
-## Guide to Working with Multiple Modules in Maven 4
+# Guide to Working with Multiple Modules in Maven 4
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
diff --git a/content/markdown/guides/mini/guide-resolver-transport.md
b/content/markdown/guides/mini/guide-resolver-transport.md
index 025b5918..3b9d5d61 100644
--- a/content/markdown/guides/mini/guide-resolver-transport.md
+++ b/content/markdown/guides/mini/guide-resolver-transport.md
@@ -1,4 +1,4 @@
-## Guide for Resolver Transport
+# Guide for Resolver Transport
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
diff --git a/content/markdown/issue-management.md
b/content/markdown/issue-management.md
index b804a819..fa6fa33a 100644
--- a/content/markdown/issue-management.md
+++ b/content/markdown/issue-management.md
@@ -1,4 +1,4 @@
-## Overview
+# Overview
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
diff --git a/content/markdown/maven-1.x-eol.md
b/content/markdown/maven-1.x-eol.md
index 7053d493..376e8f6a 100644
--- a/content/markdown/maven-1.x-eol.md
+++ b/content/markdown/maven-1.x-eol.md
@@ -1,4 +1,4 @@
-## End Of Life Apache Maven 1.x
+# End Of Life Apache Maven 1.x
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
diff --git a/content/markdown/maven-conventions.md
b/content/markdown/maven-conventions.md
index cb2aa3d9..66d2aa74 100644
--- a/content/markdown/maven-conventions.md
+++ b/content/markdown/maven-conventions.md
@@ -1,4 +1,4 @@
-## Maven Conventions
+# Maven Conventions
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
diff --git a/content/markdown/maven-logging.md
b/content/markdown/maven-logging.md
index dfcd95c1..cb0a907d 100644
--- a/content/markdown/maven-logging.md
+++ b/content/markdown/maven-logging.md
@@ -56,7 +56,7 @@ apache-maven-3.x.y
└── ...
</pre></div>
-## Configuring logging
+## Configuring logging
To configure logging with the [SLF4J Simple][2], you can edit the properties
in the
`${maven.home}/conf/logging/simplelogger.properties` file. Please see the
linked reference documentation
diff --git a/content/markdown/privacy-policy.md
b/content/markdown/privacy-policy.md
index 58af3d03..e190c88d 100644
--- a/content/markdown/privacy-policy.md
+++ b/content/markdown/privacy-policy.md
@@ -1,4 +1,4 @@
-## Privacy Policy
+# Privacy Policy
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
diff --git a/content/markdown/release-notes-all.md.vm
b/content/markdown/release-notes-all.md.vm
index 2652a950..90627066 100644
--- a/content/markdown/release-notes-all.md.vm
+++ b/content/markdown/release-notes-all.md.vm
@@ -17,7 +17,7 @@ KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
-## Release Notes
+$esc.h$esc.h Release Notes
See [Maven Releases History](docs/history.html) for more friendly view.
diff --git a/content/markdown/repository-management.md
b/content/markdown/repository-management.md
index faff0eba..17c47762 100644
--- a/content/markdown/repository-management.md
+++ b/content/markdown/repository-management.md
@@ -1,4 +1,4 @@
-## Best Practice - Using a Repository Manager
+# Best Practice - Using a Repository Manager
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
@@ -24,7 +24,7 @@ The usage of a repository manager is
considered an essential best practice for any significant usage of Maven.
-### Purpose
+## Purpose
A repository manager serves these essential purposes:
@@ -33,7 +33,7 @@ A repository manager serves these essential purposes:
* provide repositories as a deployment destination for your Maven project
outputs
-### Benefits and Features
+## Benefits and Features
Using a repository manager provides the following benefits and features:
@@ -48,7 +48,7 @@ also QA or operations teams or even customers
* provides an effective platform for exchanging binary artifacts within
your organization and beyond without the need for building artifact from source
-### Available Repository Managers
+## Available Repository Managers
The following list (alphabetical order) of open source and commercial
repository
managers are known to support the repository format used by Maven. Please
refer to the respective linked web sites for further information about
repository management in general
diff --git a/content/markdown/repository/layout.md
b/content/markdown/repository/layout.md
index 8f8a2d83..1e8184e5 100644
--- a/content/markdown/repository/layout.md
+++ b/content/markdown/repository/layout.md
@@ -1,4 +1,4 @@
-## Maven2 Repository Layout
+# Maven2 Repository Layout
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
diff --git a/content/markdown/security.md b/content/markdown/security.md
index 6ef1552d..4a4f794b 100644
--- a/content/markdown/security.md
+++ b/content/markdown/security.md
@@ -1,4 +1,4 @@
-## Maven Security
+# Maven Security
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
@@ -17,7 +17,7 @@ KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
-### Security Model
+## Security Model
The purpose of Maven is to perform the actions defined in the supplied
`pom.xml`, which commonly includes compiling and running the associated
@@ -29,7 +29,7 @@ the code, dependencies and repositories that are used in your
build.
If you want to use Maven to build untrusted code, it is up to you to
provide the required isolation.
-### Security Vulnerabilities
+## Security Vulnerabilities
Please note that binary patches are not produced for individual
vulnerabilities. To obtain the binary fix for a particular vulnerability
@@ -39,7 +39,7 @@ has been fixed.
For more information about reporting vulnerabilities, see the [Apache
Security Team](https://www.apache.org/security/) page.
-#### CVE-2021-26291 Apache Maven 3.8.1
+### CVE-2021-26291 Apache Maven 3.8.1
Severity: Medium
@@ -58,7 +58,7 @@ and we added a new `external:http:*` mirror selector (like
existing `external:*`
The decision was made to block such external HTTP repositories by default:
this is done by providing a mirror in the `conf/settings.xml` blocking insecure
HTTP external URLs.
Note: this is a vulnerability in case you're connectioning directly to remote
repositories instead of using an artifact repository manager.
-#### Maven Dependency, EAR, Javadoc, WAR and Plugin Plugins
+### Maven Dependency, EAR, Javadoc, WAR and Plugin Plugins
Severity: Low
@@ -86,7 +86,7 @@ See [full description](./security-plexus-archiver.html) for
more details.
Credit: This issue was identified by the Snyk Security Research Team
-#### CVE-2013-0253 Apache Maven 3.0.4
+### CVE-2013-0253 Apache Maven 3.0.4
Severity: Medium
@@ -110,7 +110,7 @@ All users are recommended to upgrade to [Apache Maven
Credit: This issue was identified by Graham Leggett
-#### CVE-2012-6153 Apache Maven Wagon :: WebDAV Provider
+### CVE-2012-6153 Apache Maven Wagon :: WebDAV Provider
Severity: Medium
diff --git a/content/markdown/settings.md b/content/markdown/settings.md
index e7cfdcd2..074ce3d5 100644
--- a/content/markdown/settings.md
+++ b/content/markdown/settings.md
@@ -1,4 +1,4 @@
-## Settings Reference
+# Settings Reference
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
diff --git a/content/markdown/what-is-maven.md
b/content/markdown/what-is-maven.md
index 9a8f73d4..bb848972 100644
--- a/content/markdown/what-is-maven.md
+++ b/content/markdown/what-is-maven.md
@@ -1,4 +1,4 @@
-## Introduction
+# Introduction
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
