Skip to content

Commit a9fb1b0

Browse files
AJIXuMuKVesaJuvonen
authored andcommitted
Fix of SharePoint#3650 from sp-dev-docs (SharePoint#3657)
Fix of Issue SharePoint#3650
1 parent 0463e26 commit a9fb1b0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/spfx/integrate-with-teams-introduction.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ There is an alternative way to deploy your solution which will for instance allo
6464
6565
![Solution structure](../images/sp-teams-solution-structure.png)
6666
67-
1. Notice that there are 2 image files in there. Add the manifest file you created as described in [Create Microsoft Teams manifest manually for a web part and deploy it to Microsoft Teams](./guidance/web-parts/creating-team-manifest-manually-for-webpart.md) to this folder and call it ```manifest.json```.
67+
1. Notice that there are 2 image files in there. Add the manifest file you created as described in [Create Microsoft Teams manifest manually for a web part and deploy it to Microsoft Teams](./web-parts/guidance/creating-team-manifest-manually-for-webpart.md) to this folder and call it ```manifest.json```.
6868
6969
1. In the JSON above we inserted some placeholders. Replace them as follows (notice that placeholders can occur several times):
7070
@@ -157,4 +157,4 @@ Page context in a web part has by default a reference to the Teams JavaScript SD
157157
158158
## See also
159159

160-
- [Building Microsoft Teams tab using SharePoint Framework - Tutorial](web-parts/get-started/using-web-part-as-ms-teams-tab.md)
160+
- [Building Microsoft Teams tab using SharePoint Framework - Tutorial](web-parts/get-started/using-web-part-as-ms-teams-tab.md)

0 commit comments

Comments
 (0)