Skip to content

Commit c8e9c74

Browse files
authored
Update use-sp-pnp-js-with-spfx-web-parts.md
Closing SharePoint#7957
1 parent 7e9c930 commit c8e9c74

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ There are [two ways](https://pnp.github.io/pnpjs/getting-started) to ensure that
144144

145145
## Add a project configuration file
146146

147-
Next, let's create a project configuration file for PnPjs. This file allows us to set up the imports we will need for hte project as well as initialize a instance of the sp object for use on any of our other components.
147+
Next, let's create a project configuration file for PnPjs. This file allows us to set up the imports we will need for the project as well as initialize a instance of the sp object for use on any of our other components.
148148

149149
Note all the imports for webs, lists, items, and batching. In our component we will be making calls to get items from a library, so we need to include those imports for future reference. In addition we create a variable that will hold our configured instance of the `SharePoint Querable` that will be created with the factory instance. If you'll recall from our `onInit` function above we're calling the exported getSP with the SPFx context passed in as a property. By doing so we're able to establish context with the PnPjs library so that we can subsequently make calls to the SharePoint API. Subsequent calls to `getSP` without the context will return the object that has alredy been configured.
150150

0 commit comments

Comments
 (0)