From: G. Ann Campbell Date: Wed, 23 Jan 2019 12:04:39 +0000 (+0100) Subject: DOCS formatting glitches & minor rewording (#1191) X-Git-Tag: 7.7~227 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=fefdb9803b6bf32b52d05b51efed38211e075ced;p=sonarqube.git DOCS formatting glitches & minor rewording (#1191) * extra pipe * missing table header delimiter * tangled bold and link * update description for recent versions * add missing spaces to make linebreaks work * wording tweak * revert markup order --- diff --git a/server/sonar-docs/src/pages/faq.md b/server/sonar-docs/src/pages/faq.md index eab2b9ebd6b..ccda9794bb4 100644 --- a/server/sonar-docs/src/pages/faq.md +++ b/server/sonar-docs/src/pages/faq.md @@ -6,10 +6,10 @@ url: /faq/ ## Table of Contents ## How do I get rid of issues that are False-Positives? -**False-Positive and Won't Fix** +**False-Positive and Won't Fix** You can mark individual issues False Positive or Won't Fix through the issues interface. If you're using Short-lived branch and PR analysis provided by the Developer Edition, issues marked False Positive or Won't Fix will retain that status after merge. This is the preferred approach. -**//NOSONAR** +**//NOSONAR** Most language analyzers support the use of the generic mechanism: `//NOSONAR` at the end of the line of the issue. This will suppress the all issues - now and in the future - that might be raised on the line. ## How do I find and remove projects that haven't been analyzed in a while? diff --git a/server/sonar-docs/src/pages/instance-administration/monitoring.md b/server/sonar-docs/src/pages/instance-administration/monitoring.md index 1b9036c8991..a816c8223c3 100644 --- a/server/sonar-docs/src/pages/instance-administration/monitoring.md +++ b/server/sonar-docs/src/pages/instance-administration/monitoring.md @@ -87,6 +87,7 @@ All these MBeans are read-only. It's not possible to modify or reset their value [[collapse]] | ## SonarQube MBean | Attribute Name | Description +| ---|--- | LogLevel | Log Level: INFO, DEBUG, TRACE | ServerId | SonarQube Server ID | Version | SonarQube Version diff --git a/server/sonar-docs/src/pages/previous-versions.md b/server/sonar-docs/src/pages/previous-versions.md index c4fdac47b89..50879048833 100644 --- a/server/sonar-docs/src/pages/previous-versions.md +++ b/server/sonar-docs/src/pages/previous-versions.md @@ -5,7 +5,7 @@ url: /previous-versions/ **Not using the latest and greatest version of SonarQube?** -Here are the links to the documentation of previous versions: +Links to recently archived versions are available from the navigation of this site. For older versions, see below: * [Documentation for 7.3](https://docs.sonarqube.org/display/SONARQUBE73) * [Documentation for 7.2](https://docs.sonarqube.org/display/SONARQUBE72) diff --git a/server/sonar-docs/src/pages/project-administration/managing-project-history.md b/server/sonar-docs/src/pages/project-administration/managing-project-history.md index f3315428c65..c515c88110f 100644 --- a/server/sonar-docs/src/pages/project-administration/managing-project-history.md +++ b/server/sonar-docs/src/pages/project-administration/managing-project-history.md @@ -13,7 +13,7 @@ Occasionally, you may need to manually delete a project snapshot, whether becaus [[warning]] |**About deleting snapshots**

|Deleting a snapshot is a 2-step process:

-|* The snapshot must first be removed from the project history by clicking on Delete snapshot. It |won't be displayed anymore on this History page but will still be present in the database. +|* The snapshot must first be removed from the project history by clicking on Delete snapshot. It won't be displayed anymore on this History page but will still be present in the database. |* The snapshot is actually deleted during the next project analysis. At project level, from the front page **Activity** list, choose **Show More** to see the full activity list.