Skip to content

Commit 4a5ffee

Browse files
authored
Clean up a few pages
1 parent a79e5ab commit 4a5ffee

File tree

3 files changed

+12
-13
lines changed

3 files changed

+12
-13
lines changed

docs/code-quality/quick-start-code-analysis-for-c-cpp.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ You can improve the quality of your application by running code analysis regular
1919

2020
1. To run code analysis every time the project is built using the selected configuration, select the **Enable Code Analysis on Build** check box. You can also run code analysis manually by opening the **Analyze** menu and then choosing **Run Code Analysis on** *ProjectName* or **Run Code Analysis on File**.
2121

22-
1. Choose the [rule set](using-rule-sets-to-specify-the-cpp-rules-to-run.md) that you want to use or create a [custom rule set](using-rule-sets-to-specify-the-cpp-rules-to-run.md#to-create-a-rule-set-in-a-text-editor). If using LLVM/clang-cl, see [Using Clang-Tidy in Visual Studio](../code-quality/clang-tidy.md) to configure Clang-Tidy analysis options.
22+
1. Choose the [rule set](using-rule-sets-to-specify-the-cpp-rules-to-run.md) that you want to use or create a [custom rule set](using-rule-sets-to-specify-the-cpp-rules-to-run.md#to-create-a-rule-set-in-a-text-editor). If using LLVM/clang-cl, see [Using Clang-Tidy in Visual Studio](clang-tidy.md) to configure Clang-Tidy analysis options.
2323

2424
### Standard C/C++ rule sets
2525

@@ -128,4 +128,4 @@ You can search long lists of warning messages and you can filter warnings in mul
128128

129129
## See also
130130

131-
- [Code analysis for C/C++](../code-quality/code-analysis-for-c-cpp-overview.md)
131+
- [Code analysis for C/C++](code-analysis-for-c-cpp-overview.md)

docs/code-quality/understanding-sal.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
2-
description: "Learn more about: Understanding SAL"
32
title: Understanding SAL
3+
description: "Learn more about: Understanding SAL"
44
ms.date: 11/04/2016
55
ms.topic: "conceptual"
6-
ms.assetid: a94d6907-55f2-4874-9571-51d52d6edcfd
76
---
87
# Understanding SAL
98

@@ -384,18 +383,18 @@ Here are some guidelines:
384383

385384
- Annotate value-range annotations so that Code Analysis can ensure buffer and pointer safety.
386385

387-
- Annotate locking rules and locking side effects. For more information, see [Annotating Locking Behavior](../code-quality/annotating-locking-behavior.md).
386+
- Annotate locking rules and locking side effects. For more information, see [Annotating Locking Behavior](annotating-locking-behavior.md).
388387

389388
- Annotate driver properties and other domain-specific properties.
390389

391390
Or you can annotate all parameters to make your intent clear throughout and to make it easy to check that annotations have been done.
392391

393392
## See also
394393

395-
- [Using SAL Annotations to Reduce C/C++ Code Defects](../code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md)
396-
- [Annotating Function Parameters and Return Values](../code-quality/annotating-function-parameters-and-return-values.md)
397-
- [Annotating Function Behavior](../code-quality/annotating-function-behavior.md)
398-
- [Annotating Structs and Classes](../code-quality/annotating-structs-and-classes.md)
399-
- [Annotating Locking Behavior](../code-quality/annotating-locking-behavior.md)
400-
- [Specifying When and Where an Annotation Applies](../code-quality/specifying-when-and-where-an-annotation-applies.md)
401-
- [Best Practices and Examples](../code-quality/best-practices-and-examples-sal.md)
394+
- [Using SAL Annotations to Reduce C/C++ Code Defects](using-sal-annotations-to-reduce-c-cpp-code-defects.md)
395+
- [Annotating Function Parameters and Return Values](annotating-function-parameters-and-return-values.md)
396+
- [Annotating Function Behavior](annotating-function-behavior.md)
397+
- [Annotating Structs and Classes](annotating-structs-and-classes.md)
398+
- [Annotating Locking Behavior](annotating-locking-behavior.md)
399+
- [Specifying When and Where an Annotation Applies](specifying-when-and-where-an-annotation-applies.md)
400+
- [Best Practices and Examples](best-practices-and-examples-sal.md)

docs/code-quality/using-the-cpp-core-guidelines-checkers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -317,7 +317,7 @@ Because of the way the code analysis rules get loaded within Visual Studio 2015,
317317

318318
1. In the **NuGet Package Manager** window, search for Microsoft.CppCoreCheck.
319319

320-
![Nuget Package Manager window showing the CppCoreCheck package.](../code-quality/media/cppcorecheck_nuget_window.png)
320+
![Nuget Package Manager window showing the CppCoreCheck package.](media/cppcorecheck_nuget_window.png)
321321

322322
1. Select the Microsoft.CppCoreCheck package and then choose the **Install** button to add the rules to your project.
323323

0 commit comments

Comments
 (0)