Skip to content

Commit 8e9826c

Browse files
dannyjesseeVesaJuvonen
authored andcommitted
Cleaned up references for placeholder example (SharePoint#814)
There was some inconsistency in the "Getting access to page placeholders" section that referred to the header/PageHeader identifier although the example code was for the Bottom placeholder.
1 parent 3fd8b8d commit 8e9826c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,10 @@ You can also follow these steps by watching the video on the [SharePoint PnP You
1818

1919
Application Customizer extensions are supported with `Site`, `Web` and `List` scopes. You can control the scope by deciding where or how the Application Customizer will be registered in your SharePoint tenant. When the Application Customizer exists in the scope and is being rendered, you can use the following method to get access to the placeholder. Once you have received the placeholder object, you have full control over what will be presented to the end user.
2020

21-
Notice that we are requesting a well-known placeholder by using the corresponding well-known identifier. In this case, the code is accessing the header section of the page using the `PageHeader` identifier.
21+
Notice that we are requesting a well-known placeholder by using the corresponding well-known identifier. In this case, the code is accessing the footer section of the page using the `Bottom` identifier.
2222

2323
```ts
24-
// Handling the header placeholder
24+
// Handling the Bottom placeholder
2525
if (!this._bottomPlaceholder) {
2626
this._bottomPlaceholder =
2727
this.context.placeholderProvider.tryCreateContent(

0 commit comments

Comments
 (0)