Skip to content

Commit 85409c6

Browse files
authored
Merge pull request MicrosoftDocs#2062 from corob-msft/cr-https-mostly
Bulk update all http links to https, where supported.
2 parents 3318b91 + 9ca0124 commit 85409c6

File tree

69 files changed

+98
-98
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

69 files changed

+98
-98
lines changed

docs/assembler/arm/arm-assembler-diagnostic-messages.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The Microsoft ARM assembler (*armasm*) emits diagnostic warnings and errors when
1717

1818
> A2193: this instruction generates unpredictable behavior
1919
20-
The ARM architecture cannot guarantee what happens when this instruction is executed. For details about the well-defined forms of this instruction, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/p/?linkid=246464).
20+
The ARM architecture cannot guarantee what happens when this instruction is executed. For details about the well-defined forms of this instruction, consult the [ARM Architecture Reference Manual](https://go.microsoft.com/fwlink/p/?linkid=246464).
2121

2222
```asm
2323
ADD r0, r8, pc ; A2193: this instruction generates unpredictable behavior
@@ -93,7 +93,7 @@ In ARM mode, there is an alternate syntax for specifying constants. Instead of
9393

9494
> A4509: This form of conditional instruction is deprecated
9595
96-
This form of conditional instruction has been deprecated by ARM in the ARMv8 architecture. We recommend that you change the code to use conditional branches. To see which conditional instructions are still supported, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/p/?linkid=246464).
96+
This form of conditional instruction has been deprecated by ARM in the ARMv8 architecture. We recommend that you change the code to use conditional branches. To see which conditional instructions are still supported, consult the [ARM Architecture Reference Manual](https://go.microsoft.com/fwlink/p/?linkid=246464).
9797

9898
This warning is not emitted when the **-oldit** command-line switch is used.
9999

docs/build/arm-exception-handling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The ARM EABI (embedded application binary interface) specifies an exception unwi
1515

1616
### Assumptions
1717

18-
Executable images for Windows on ARM use the Portable Executable (PE) format. For more information, see [Microsoft PE and COFF Specification](http://go.microsoft.com/fwlink/p/?linkid=84140). Exception handling information is stored in the .pdata and .xdata sections of the image.
18+
Executable images for Windows on ARM use the Portable Executable (PE) format. For more information, see [Microsoft PE and COFF Specification](https://go.microsoft.com/fwlink/p/?linkid=84140). Exception handling information is stored in the .pdata and .xdata sections of the image.
1919

2020
The exception handling mechanism makes certain assumptions about code that follows the ABI for Windows on ARM:
2121

docs/build/reference/hlsl-property-pages.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,10 @@ You can use the HLSL compiler (fxc.exe) property pages to configure how individu
2020

2121
Provides properties to specify how files are output by the HLSL compiler.
2222

23-
You can specify command-line arguments to the HLSL compiler by using the **Additional Options** property of the **Command Line** property page; this includes arguments that can't be configured by using other properties of the HLSL property pages. For information about the HLSL compiler, see [Effect-Compiler Tool](http://go.microsoft.com/fwlink/p/?LinkID=258285&clcid=0x409)
23+
You can specify command-line arguments to the HLSL compiler by using the **Additional Options** property of the **Command Line** property page; this includes arguments that can't be configured by using other properties of the HLSL property pages. For information about the HLSL compiler, see [Effect-Compiler Tool](https://go.microsoft.com/fwlink/p/?LinkID=258285&clcid=0x409)
2424

2525
## See also
2626

2727
[C++ project property page reference](property-pages-visual-cpp.md)<br>
2828
[Command Line Property Pages](command-line-property-pages.md)<br>
29-
[Compiling Shaders](http://go.microsoft.com/fwlink/p/?LinkID=258284&clcid=0x409)
29+
[Compiling Shaders](https://go.microsoft.com/fwlink/p/?LinkID=258284&clcid=0x409)

docs/cppcx/codesnippet/CPP/clientapp/app.xaml.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ using namespace Windows::UI::Xaml::Interop;
2222
using namespace Windows::UI::Xaml::Media;
2323
using namespace Windows::UI::Xaml::Navigation;
2424

25-
// The Blank Application template is documented at http://go.microsoft.com/fwlink/p/?linkid=234227
25+
// The Blank Application template is documented at https://go.microsoft.com/fwlink/p/?linkid=234227
2626

2727
/// <summary>
2828
/// Initializes the singleton application object. This is the first line of authored code

docs/cppcx/codesnippet/CPP/clientapp/mainpage.xaml.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ using namespace Windows::UI::Xaml::Navigation;
2222

2323
using namespace DelegatesEvents;
2424

25-
// The Blank Page item template is documented at http://go.microsoft.com/fwlink/p/?linkid=234238
25+
// The Blank Page item template is documented at https://go.microsoft.com/fwlink/p/?linkid=234238
2626

2727
MainPage::MainPage()
2828
{

docs/cppcx/codesnippet/CPP/eventsupportinvs/app.xaml.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ using namespace Windows::UI::Xaml::Interop;
2222
using namespace Windows::UI::Xaml::Media;
2323
using namespace Windows::UI::Xaml::Navigation;
2424

25-
// The Blank Application template is documented at http://go.microsoft.com/fwlink/p/?linkid=234227
25+
// The Blank Application template is documented at https://go.microsoft.com/fwlink/p/?linkid=234227
2626

2727
/// <summary>
2828
/// Initializes the singleton application object. This is the first line of authored code

docs/cppcx/codesnippet/CPP/eventsupportinvs/mainpage.xaml.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ using namespace Windows::UI::Xaml::Input;
1919
using namespace Windows::UI::Xaml::Media;
2020
using namespace Windows::UI::Xaml::Navigation;
2121

22-
// The Blank Page item template is documented at http://go.microsoft.com/fwlink/p/?linkid=234238
22+
// The Blank Page item template is documented at https://go.microsoft.com/fwlink/p/?linkid=234238
2323

2424
MainPage::MainPage()
2525
{

docs/error-messages/compiler-errors-2/compiler-error-c2659.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.assetid: b0883600-4d27-4ca7-a931-8ca6bd48654d
99

1010
'operator' : function as left operand
1111

12-
A function was on the left side of the specified operator. The most common reason for this error is that the compiler has parsed the identifier on the left side of the operator as a function when the developer intended it to be a variable. For more information, see Wikipedia article [Most vexing parse](http://en.wikipedia.org/wiki/Most_vexing_parse). This example shows a function declaration and a variable definition that are easily confused:
12+
A function was on the left side of the specified operator. The most common reason for this error is that the compiler has parsed the identifier on the left side of the operator as a function when the developer intended it to be a variable. For more information, see Wikipedia article [Most vexing parse](https://en.wikipedia.org/wiki/Most_vexing_parse). This example shows a function declaration and a variable definition that are easily confused:
1313

1414
```
1515
// C2659a.cpp

docs/error-messages/compiler-errors-2/compiler-error-c3872.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.assetid: 519e95be-5641-40cc-894c-da4819506604
1111

1212
The C++ compiler follows the C++11 standard on characters allowed in an identifier. Only certain ranges of characters and universal character names are allowed in an identifier. Additional restrictions apply to the initial character of an identifier. For more information and a list of allowed characters and universal character name ranges, see [Identifiers](../../cpp/identifiers-cpp.md).
1313

14-
The range of characters allowed in an identifier is less restrictive when compiling C++/CLI code. Identifiers in code compiled by using /clr should follow [Standard ECMA-335: Common Language Infrastructure (CLI)](http://www.ecma-international.org/publications/standards/Ecma-335.htm).
14+
The range of characters allowed in an identifier is less restrictive when compiling C++/CLI code. Identifiers in code compiled by using /clr should follow [Standard ECMA-335: Common Language Infrastructure (CLI)](https://www.ecma-international.org/publications/standards/Ecma-335.htm).
1515

1616
The following sample generates C3872:
1717

docs/error-messages/compiler-errors-2/compiler-error-c3873.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.assetid: e68fd3be-2391-492b-ac3f-d2428901b2e9
1111

1212
The C++ compiler follows the C++11 standard on characters allowed in an identifier. Only certain ranges of characters and universal character names are allowed in an identifier. Additional restrictions apply to the initial character of an identifier. For more information and a list of allowed characters and universal character name ranges, see [Identifiers](../../cpp/identifiers-cpp.md).
1313

14-
The range of characters allowed in an identifier is less restrictive when compiling C++/CLI code. Identifiers in code compiled by using /clr should follow [Standard ECMA-335: Common Language Infrastructure (CLI)](http://www.ecma-international.org/publications/standards/Ecma-335.htm).
14+
The range of characters allowed in an identifier is less restrictive when compiling C++/CLI code. Identifiers in code compiled by using /clr should follow [Standard ECMA-335: Common Language Infrastructure (CLI)](https://www.ecma-international.org/publications/standards/Ecma-335.htm).
1515

1616
The following sample generates C3873:
1717

0 commit comments

Comments
 (0)